-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Supporting the nightly flag -Zmultitarget #19
Conversation
I see where the issue arises, the loop in the method which constructs the process command is pretty much useless as it just overrides the previous iteration. Although, the dynamic environment variables are related to the linker, and they are being bound to a specific target which seems ok. I can't have an idea why the CI would fail that much really...
|
Looks like it's not using our linker wrapper script. |
It's not working, maybe you can add some |
It just compiled fine on my end, I don't know why the CI would fail, it also looks for
|
Yes, it should be lower case. |
The nightly test failure is unrelated to this change: briansmith/ring#1469 |
What can it be then? |
I don't know, opened rust-lang/rust#95267. |
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.
Looks good to me, thanks!
Released in v0.7.0: https://crates.io/crates/cargo-zigbuild/0.7.0 |
First of all I want to say thank you for this incredible tool, it made our work so much easier.
As a part of our pipe line we need to build our program to multiple targets, recently a change has been made to the
cargo
cli allowing to pass a flag calledmultitarget
which makes it possible to compile to multiple targets all at once.The proposed changes follow the way the
cargo build
CLI works, see:https://github.dev/rust-lang/cargo/blob/06b9d31743210b788b130c8a484c2838afa6fc27/src/bin/cargo/commands/build.rs
suggesting that
target
should infact be a flag which may occur N >= 1 amount of times.This pull request makes it possible to run the next:
cargo-zigbuild.exe build -Zmultitarget --target x86_64-pc-windows-msvc --target x86_64-unknown-linux-musl --release