pw_build: Remove old flag requirement

The very important --incompatible_enable_cc_toolchain_resolution was flipped to enabled by default in Bazel 7.0.0, and no longer needs to be manually set. Change-Id: Ic74272d57c857908ab8b9bb1d9b23e0d630d2e18 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259252 Docs-Not-Needed: Armando Montanez <[email protected]> Reviewed-by: Ted Pudlik <[email protected]> Lint: Lint 🤖 <[email protected]> Pigweed-Auto-Submit: Armando Montanez <[email protected]> Presubmit-Verified: CQ Bot Account <[email protected]> Commit-Queue: Auto-Submit <[email protected]>
google · Jan 9, 2025 · 78a218f · 78a218f
1 parent d3a0a19
commit 78a218f
Showing 1 changed file with 0 additions and 3 deletions.
diff --git a/pw_build/pigweed.bazelrc b/pw_build/pigweed.bazelrc
@@ -23,9 +23,6 @@
 # pw_transfer/py/pw_transfer.
 common --incompatible_default_to_explicit_init_py
 
-# Required for new toolchain resolution API.
-build --incompatible_enable_cc_toolchain_resolution
-
 # Do not attempt to configure an autodetected (local) toolchain. We vendor all
 # our toolchains, and CI VMs may not have any local toolchain to detect.
 common --repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1