The corpus had ZERO bundler coverage (the stream's named top risk). Add a `.build` `bundle` directive to the corpus runner: after a successful `aot` build it asserts each `expect` entry exists under the produced `.app` (repo-relative), then `rm -rf`s it. macOS-host only — the `.app` + codesign are Apple-specific, so the example is skipped on other hosts. `examples/1665-platform-macos-bundle-smoke.sx` sets `bundle_path`/`bundle_id` via a `#run` config; `default_pipeline` auto-bundles (build.sx imports the bundler, no explicit `on_build` needed). The directive asserts `Contents/MacOS`, `Contents/Info.plist`, `Contents/_CodeSignature`. Verified: passes on BOTH gates (the bundler runs on the legacy interp AND the VM), the `.app` is cleaned up, and a bad `expect` entry correctly fails (the check is not vacuous). Unit test + CLAUDE.md `.build`-directive docs updated. 706/0 both gates.
22 lines
801 B
Plaintext
22 lines
801 B
Plaintext
// macOS `.app` bundle smoke test — the corpus's first real bundler coverage.
|
|
//
|
|
// `default_pipeline` auto-bundles when `bundle_path` is set (build.sx imports the
|
|
// sx bundler, so no explicit `on_build` is needed). `sx build` runs the bundler
|
|
// after link, producing a signed `.app`. The `.build` `bundle` directive asserts
|
|
// the `.app` structure (`Contents/MacOS`, `Info.plist`, `_CodeSignature`) and then
|
|
// cleans it up. macOS-host ONLY — the directive skips the example on other hosts.
|
|
|
|
#import "modules/std.sx";
|
|
|
|
configure :: () abi(.compiler) {
|
|
opts := build_options();
|
|
opts.set_bundle_path(".sx-tmp/1665-platform-macos-bundle-smoke.app");
|
|
opts.set_bundle_id("co.example.bundlesmoke");
|
|
}
|
|
#run configure();
|
|
|
|
main :: () -> i32 {
|
|
print("bundle smoke ok\n");
|
|
return 0;
|
|
}
|