-
Notifications
You must be signed in to change notification settings - Fork 517
Set ARFLAGS in the cargo_build_script rule #3704
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
base: main
Are you sure you want to change the base?
Conversation
553c3f0 to
e0e5ddc
Compare
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.
Seems reasonable to me! Would you also be able to add some sort of regression test to //test/cargo_build_script/...? I would love to know the plumbing of AR args continues to work.
edit: Also, thank you!
|
Looks like the macOS failure is very relevant; the configured toolchain's |
Hmm... or not. Looks like it's failing on other builds too. Test log contents: |
There were two issues with AR in the cargo_build_script rule: 1. ARFLAGS was not set. 2. For many toolchains, the ar tool was not properly configured. This change fixes both of those problems.
c9aee18 to
dc09d91
Compare
|
Hmm, TL;DR: cc-rs does not properly support |
|
I'd much rather emit an error if I'll try to add |
This was preventing ar flags from propagating to the cargo build script runner.