- add runnable examples for an unknown-name Tool, multi-export plugin, external kernel provider and same-name multi-version packages - add JSON Schemas for Analysis v1, Trace v1 and Tool v1 and validate them in CI - extend CI with protocol/consumer smoke tests and a Windows/macOS cargo check - add --kernel provider descriptors and R6 example integration tests - document the examples and update M0.6 status
18 lines
718 B
Markdown
18 lines
718 B
Markdown
# Multi-export plugin example
|
|
|
|
One native library exports two complete names: `solver.add` and `solver.neg`.
|
|
Both are registered and callable; there is no "first prefix wins" namespace.
|
|
|
|
```sh
|
|
./examples/plugin-multi-export/build.sh
|
|
marqdo check examples/plugin-multi-export/plugin-call.mq.md \
|
|
--plugin examples/plugin-multi-export
|
|
marqdo run examples/plugin-multi-export/plugin-call.mq.md \
|
|
--plugin examples/plugin-multi-export \
|
|
--trust-native-plugin --allow-plugin demo.solver
|
|
```
|
|
|
|
`check --plugin` validates both signatures without loading the library. The
|
|
runtime still requires the explicit in-process trust decision; a C ABI is not a
|
|
sandbox, and an isolated worker transport is not part of this build.
|