diff options
author | Keith Smiley <keithbsmiley@gmail.com> | 2023-09-22 11:06:18 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-09-22 13:06:18 -0500 |
commit | 45daa81ec696de891ecb5c4d4b6f3bdf99b19e03 (patch) | |
tree | f0426987b9316a94ad1beec4bd3222247e6bd96d | |
parent | feb90e8e7a92381001cf2f2052a7fd982b28ee26 (diff) | |
download | bazelbuild-apple_support-45daa81ec696de891ecb5c4d4b6f3bdf99b19e03.tar.gz |
Update toolchain setup docs (#265)
https://github.com/bazelbuild/rules_cc/pull/199
-rw-r--r-- | README.md | 19 |
1 files changed, 12 insertions, 7 deletions
@@ -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 |