feat: Support ABI selection and transition #169
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 ABI (libc type and version) is taken from the ABI component of the target triple. Hence, no real additional support is required. The existing target selection support is sufficient.
However, Bazel's bazelbuild/platforms does not capture ABI constraints. Therefore, we add an ABI constraint setting and constraint values to rules_zig. Note, that users do not necessarily have to use these. If needed they can define their own ABI constraint setting and values and define and register toolchains using these targets.
The default ABI was previously left undeclared in the toolchain declarations. This is changed to default to GNU on Linux and Windows and none on MacOS. Previously, Zig would default to musl on Linux, which is not a bad choice in general, but causes issues when trying to combine Zig generated binaries with Bazel built C/C++ binaries. If users want to use musl then they can do so by explicitly configuring a target platform that sets the musl abi constraint.
Closes #54
Closes #55