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

Pass the configure-time environment vars to build steps? #126

Open
jimporter opened this issue Dec 21, 2019 · 1 comment
Open

Pass the configure-time environment vars to build steps? #126

jimporter opened this issue Dec 21, 2019 · 1 comment
Labels
Milestone

Comments

@jimporter
Copy link
Owner

To reduce potentially-confusing errors, maybe it'd make sense to use the environment vars as specified during configuration when running any build step (e.g. by creating a command like bfg9000 run and prepending that to every command in the build scripts).

This came up while working on caliber where I noticed that temporarily setting CXX during configuration results in the build forgetting about this by the time caliber actually runs, meaning that it's easy to accidentally miss testing a non-default compiler with caliber.

I'm not sure if this is something that should be fixed, or if the above suggestion is right. I'll have to think...

@jimporter jimporter added this to the future milestone Dec 21, 2019
@jimporter
Copy link
Owner Author

jimporter commented Jun 17, 2021

Note: bfg9000 run now exists, so you can technically resolve this via bfg9000 run make <whatever>. Having it as the default might be nice though (or at least an option to make it work implicitly)...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant