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
Right now it's very ad-hoc, with users specifying link_args of unspecified format, tied to C compiler implementation, propogating linker arguments between crates. It's a mess. If we don't fix this we're going to end up tied to arbitrary, platform-specific C compiler semantics. Rust should have some sort of linker model baked in that just works for most common cases.
The text was updated successfully, but these errors were encountered:
I would like to add my support for this. While the most common cases, like building simple executables or shared libraries, are reasonably well-handled by rustc right now, anything outside of that is hell to get right.
I'd like to have much more control over the compilation of rust code right now, as the uncommon cases are very difficult to get right. This is important for embedded environments and similar places.
Right now it's very ad-hoc, with users specifying link_args of unspecified format, tied to C compiler implementation, propogating linker arguments between crates. It's a mess. If we don't fix this we're going to end up tied to arbitrary, platform-specific C compiler semantics. Rust should have some sort of linker model baked in that just works for most common cases.
The text was updated successfully, but these errors were encountered: