Skip to content

0.9.2: dist-apple places deployed files at the bundle's resource destination (mcpp#630) - #22

Merged
Sunrisepeak merged 6 commits into
mainfrom
630-apple-resources
Sep 13, 2026
Merged

0.9.2: dist-apple places deployed files at the bundle's resource destination (mcpp#630)#22
Sunrisepeak merged 6 commits into
mainfrom
630-apple-resources

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

mcpp 2026.9.13.2 stages a Mach-O program's tree before the closure walk (#630, item 3a): bin/<name> and every mcpp::deploy'd file under bin/<to>/..., handed to a dispatched format with closure = not-walked in the stage manifest. dist-apple used to copy that tree whole into Contents/MacOS/, which put the executable at Contents/MacOS/bin/<name> and the resources beside it.

From 0.9.2 the launcher alone goes to the executable directory and every other top-level entry of the staged bin/ goes to the bundle's resource destination: Contents/Resources/<to>/... on macOS, the bundle root on iOS. One ditto action per entry, each an input of the bundle step.

The iOS fixture declares llvm.libcxx and llvm.compiler-rt-builtins under cfg(os = "ios"), which is what an application that imports std declares on those rows from 2026.9.13.2 (mcpp docs/20, "The C++ runtime and the compiler runtime are packages on these rows"). Both fixtures deploy a file, and the macOS CI asserts where it lands.

CI is pinned to mcpp 2026.9.13.2.

@Sunrisepeak
Sunrisepeak merged commit ca4cb63 into main Sep 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants