Enable musl target builds with vendored libgit2 #4991
+7
−4
Conversation
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
xsoheilalizadeh
changed the title
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.
Fixes #4373
Enable statically-linked musl binaries for x86_64 and aarch64 by using
vendored libgit2. This resolves the linking issues that previously
caused musl builds to fail in CI.
Changes:
musl targets in packages/cli/Cargo.toml
build targets in publish workflow
The vendored-libgit2 feature builds libgit2 from source and statically
links it, avoiding musl-specific system library linking issues. This
only affects musl builds - other platforms continue using system
libraries for faster builds.