release: v0.0.17 — macOS ARM64 support#47
Closed
Sunrisepeak wants to merge 8 commits into
Closed
Conversation
- Bump version to 0.0.17 in mcpp.toml - Add CHANGELOG entry for 0.0.17 (macOS ARM64 headline feature) - Fix release.yml macOS job: replace broken self-host approach with proven xmake direct build (matching bootstrap-macos.yml) - Use macosx-arm64 naming convention for tarball artifacts - Remove broken self-host step from ci-macos.yml
Since v0.0.16 macOS binary is available, both release and CI can now self-host: download v0.0.16 → mcpp build → produce new binary. No xmake needed.
xlings LLVM's clang++.cfg uses -nostdinc++ which suppresses the implicit -lc++ that clang++ normally adds during linking. This causes undefined symbol errors for C++ stdlib types. Fix by explicitly adding -lc++ to link flags on macOS.
v0.0.16 mcpp lacks the -lc++ fix needed for macOS self-host. Use xmake (proven working) for this release. Once v0.0.17 ships with the libc++ link fix, subsequent releases can self-host.
- .xlings.json: bump mcpp to 0.0.16 - CI/release: use `xlings install mcpp` with fallback to direct download - Removes xmake dependency from main build path
v0.0.16 mcpp lacks -lc++ for macOS linking. Use xmake in CI/release workflows as a transitional builder. xmake.lua is NOT committed to the repo — generated at build time and removed after. Once v0.0.17 binary (with the fix) is in xlings-res, future versions can self-host via `xlings install mcpp`.
Now that mcpp@0.0.16 is in xlings-res with the libc++ fix, CI and release workflows can simply: xlings install mcpp → mcpp build No xmake needed — mcpp self-hosts on macOS via xlings ecosystem.
- Add `xlings update` before install to refresh pkgindex - Bump cache key to invalidate stale xlings data
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
release.ymlmacOS job: replace broken self-host steps (libc++ linking issues) with the proven xmake direct-build approach frombootstrap-macos.ymlmacosx-arm64naming convention for release tarballs (xlings convention)ci-macos.yml, keep working xmake bootstrap and LLVM validation testsKey changes
release.yml
build-macosjob: Instead of bootstrap → self-host (which failed due to libc++ linking), we now use xmake directly:Tarball naming: Changed from
darwin-arm64tomacosx-arm64to match xlings convention.Test plan
mcpp-0.0.17-macosx-arm64.tar.gzon an Apple Silicon Mac