-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Use constraints in global conditions instead of configuration flags. #12427
Conversation
Downstream test at https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1751 (previously failing gerrit, cloudrobotics, flatbuffers) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice to see the reduced duplication.
rules_nodejs fix: bazel-contrib/rules_nodejs#2274 |
(third_party/BUILD). This is part of bazelbuild#12427, that changes third_party/BUILD file.
"//src/conditions:linux_ppc": ["cpu_profiler_posix.cc"], | ||
"//src/conditions:linux_s390x": ["cpu_profiler_posix.cc"], | ||
"//src/conditions:linux_x86_64": ["cpu_profiler_posix.cc"], | ||
"//src/conditions:linux": ["cpu_profiler_posix.cc"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice.
…lags in BUILD.tools.
…ition where appropriate.
39324fb
to
686e08d
Compare
I changed configuration settings in //src/conditions to use constraints instead of flags and then fixed some places where this is used.
I fixed uses of darwin and darwin_x86_64, which using flags I believe is the same thing and using constraints actually becomes different.
Added config_setting for linux. Used it where it makes sense. It cannot be used in tools/jdk/..., because it somehow gets new @bazel_tools and old @bazel_tools/constraints.
This might break users of remote execution or cross compiling. The users working on a single platform should be safe.