The macOS job failed with no_matching_artifact because the integration test copied the Linux-only example manifest and built a Linux-named .so. Tests now generate a manifest for the actual host triple, use the platform dynamic library name and compiler flags, and never rewrite the tracked example manifest. - add a cross-platform no_matching_artifact test that runs without a C compiler - add real tamper and ABI-major-mismatch rejection tests - make worker fixtures platform-native; Windows remains explicitly unsupported (no cc) rather than counted as a pass - example build scripts emit host-specific build/ fixtures (gitignored) - CI smoke points at the generated fixtures
18 lines
762 B
Markdown
18 lines
762 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 # writes build/ for this host
|
|
marqdo check examples/plugin-multi-export/plugin-call.mq.md \
|
|
--plugin examples/plugin-multi-export/build
|
|
marqdo run examples/plugin-multi-export/plugin-call.mq.md \
|
|
--plugin examples/plugin-multi-export/build \
|
|
--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.
|