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

support --action_env vars in build scripts #447

Merged
merged 1 commit into from
Oct 16, 2020

Conversation

dae
Copy link
Contributor

@dae dae commented Oct 16, 2020

The existing rustc_env attribute is useful when the provided env var
will not differ between machines, but is not practical when each
user of the build script may require a different value, such as passing
in a custom path to a tool on their machine.

Fixes the issue mentioned in
#314 (comment)
by starting from the default environment. I did not make a change in rustc.bzl,
so this only applies to build scripts at the moment.

The existing rustc_env attribute is useful when the provided env var
will not differ between machines, but is not practical when each
user of the build script may require a different value, such as passing
in a custom path to a tool on their machine.

Fixes the issue mentioned in
bazelbuild#314 (comment)
by starting from the default environment.
@google-cla google-cla bot added the cla: yes label Oct 16, 2020
Copy link
Collaborator

@damienmg damienmg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I would have preferred to ship it with a test but this would require a bit too much setup to everybody so LGTM.

@damienmg damienmg merged commit b2a482f into bazelbuild:master Oct 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants