feat: use libc without cc-toolchain #226
Merged
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.
The Zig compiler bundles its own libc(++). rules_zig exposes these using the targets
@rules_zig//zig/lib:libc(++)
. However, so far these were implemented ascc_library
targets, meaning that depending on them incurred a dependency on the cc-toolchain, even if the target was only used to forward a-lc(++)
linker flag.This change removes that dependency. These targets are now generated using a custom rule that is still compatible with the cc rules, but no longer requires a cc-toolchain. This greatly simplifies cross-compilation use-cases with libc(++) dependencies. For example