You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
The text was updated successfully, but these errors were encountered:
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)...
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...
The text was updated successfully, but these errors were encountered: