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
Allow templating for env vars within build, and build overrides #3580
Labels
enhancement
New feature or request
Comments
HenryNguyen5
added
enhancement
New feature or request
triage
Issue pending triage by one of the maintainers
labels
Nov 22, 2022
refs #2583 |
I don't remember why the hooks were a problem for #2583, will have to re-investigate. |
hey @HenryNguyen5 , could you give #3592 a try? |
hey @caarlos0! sorry for the late reply. I'd like to confirm that it looks like it's working with the testing I've been doing so far. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, im using cross-platform builds via
zig
, for an example you can see: https://dev.to/kristoff/zig-makes-go-cross-compilation-just-work-29hoWhat ends up happening is that I have a very long
CC
andCXX
env var that gets mostly reused across builds, but with minor changes per platform.Ex. This is what my build script looks like right now:
I previously found #2829 (comment) which states that it might not be possible, but it was awhile ago, so maybe that situation is better now.
Describe the solution you'd like
It would be nice to be able to write something like the following:
or/and be able to do the same with env fields within overrides.
Another possible solution would be to expose
CC
andCXX
as their own specific fields likeldflags
which supports templating, since they are frequently used for cross platform builds with CGO enabled.Describe alternatives you've considered
I considered this: #459
But with the amount of flags i am maintaining for
CXX
andCC
, it would result in a lot of duplication, and I am better off just using shell scripts instead which let me compose the env vars.Search
Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered: