-
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
Replace uses of cfg = "host"
with cfg = "exec"
#15785
Conversation
This increases the compatibility for builds where host and exec platform are different (e.g., with remote execution).
@bazel-io flag (not a hard blocker for 5.3, but users can't test whether they are compatible with |
@bazel-io flag |
@bazel-io fork 5.3.0 |
@gregestren @comius Can you help review this one? |
AFAIK, this is all fine. |
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.
Because cfg = "host"
is treated identically to cfg = "exec"
, this change is effectively a no-op but makes the correct usage much more clear.
This increases the compatibility for builds where host and exec platform are different (e.g., with remote execution). Closes bazelbuild#15785. PiperOrigin-RevId: 461897893 Change-Id: I734ccdd1ae13e7c625cc22c894bc482fe080d70b
This increases the compatibility for builds where host and exec platform are different (e.g., with remote execution). Closes bazelbuild#15785. PiperOrigin-RevId: 461897893 Change-Id: I734ccdd1ae13e7c625cc22c894bc482fe080d70b
This increases the compatibility for builds where host and exec platform are different (e.g., with remote execution). Closes bazelbuild#15785. PiperOrigin-RevId: 461897893 Change-Id: I734ccdd1ae13e7c625cc22c894bc482fe080d70b
This increases the compatibility for builds where host and exec platform
are different (e.g., with remote execution).