Description
Proposal
This affects only three targets: windows-gnu
, linux-musl
, -wasi
.
Currently startup objects (all three targets) and libraries (windows-gnu
) and placed next to Rust's own libraries like libstd.
This causes various problems, e.g. somebody wants to link external libraries with Rust but CRT shipped by Rust is incompatible with the one used to link external library.
For windows-gnu
there is also linker shipped.
rust-lang/rust#68887 (comment) explains how to resolve that limitation by creating native and self-contained modes. Native mode would avoid using anything located inside self-contained
directory.
rust-lang/rust#72999 is preparation that moves things but retains old user visible behaviour (everything is linked just like before, only the paths are different).
Mentors or Reviewers
Process
The main points of the Major Change Process is as follows:
- File an issue describing the proposal.
- A compiler team member or contributor who is knowledgeable in the area can second by writing
@rustbot second
.- Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a
-C flag
, then full team check-off is required. - Compiler team members can initiate a check-off via
@rfcbot fcp merge
on either the MCP or the PR.
- Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a
- Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.
You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.