Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update toolchain setup docs #265

Merged
merged 1 commit into from
Sep 22, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,13 +59,18 @@ use_repo(apple_cc_configure, "local_config_apple_cc")

### Incompatible toolchain resolution

Bazel is currently working on migrating C++ toolchain configuration to a
new discovery method that no longer uses the `--*crosstool_top` flags.
If you would like to test this upcoming feature, or need to use this in
your build for other reasons, you can use this toolchain with
`--incompatible_enable_cc_toolchain_resolution` as long as you provide a
`platform_mappings` file. Please file any issues you find as you test
this work in progress configuration.
Bazel 7.x enabled a new discovery method for CC toolchains. With this
new method you no longer need to pass any `--*crosstool_top` flags.
Instead you just need to depend on `apple_support` and bazel
automatically picks the right toolchain based on what you're building.
If you have any issues with this you can temporarily disable it with
`--incompatible_enable_cc_toolchain_resolution=false`. If you do please
file an issue here.

NOTE: If you're using bzlmod and depend on both `apple_support` and
`rules_cc` in your `MODULE.bazel`, `apple_support`'s `bazel_dep` must
come _before_ `rules_cc` in order to take precedence over the default CC
toolchains.

## Toolchain configuration

Expand Down