-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Using rustc as the linker driver for mixed C++/Rust binaries #83282
Comments
Hi.
Yes, all 3 points make sense to me and they (together with static-nobundle) are the main reasons why the RFC was written.
Implementation effort required to support all the parts of the RFC is relatively small, or at least not large.
Yes!
For each item I can provide a starting point to read-understand-modify the code from, if necessary. |
Implementation is started in #83507. |
Oh great! Thank you so much! |
This is an opening of a very likely very short design discussion for #81490.
Hi @petrochenkov, thanks so much for pushing for this! I just filed bazelbuild/rules_rust#637 to document what and why we need to be able to link mixed C++/Rust binaries with
rustc
as the linker driver. I believe what you propose will solve all our problems, but just to be sure I'd like to reiterate:--whole-archive
/--no-whole-archive
--start-lib
/--end-lib
with object files instead of a static archive. I believe we will be able to do that using--codegen=link-arg
after the proposed change to keep relative order of-l:
flags and--codegen=link-arg
respectedMy questions:
native_link_modifiers
aim to solve them?Thank you!
The text was updated successfully, but these errors were encountered: