A new proposal has been announced: #310. It will be
announced at the next meeting to try and draw attention to it,
but usually MCPs are not discussed during triage meetings. If
you think this would benefit from discussion amongst the
team, consider proposing a design meeting.
I'd be willing to second this proposal but I don't really know much about it. I'm curious to hear from @Alex Crichton as I saw that the WASI target was mentioned; I might expect @Vadim Petrochenkov to have an opinion as well.
It sounds like a reasonable proposal to me, it would indeed be nice if using our precompiled artifacts worked very easily with both external toolchains as well as with bundled support in rustc itself. The main thing I think needs to keep working is rustc by default works on platforms missing the libraries (e.g. missing mingw compiler/objects), but I suspect everyone feels the same way about that :)
@T-compiler: Proposal #310 has been seconded, and will be approved in 10 days if no objections are raised.
OK. Well let's kick off FCP and see if anyone has any concerns in the meantime..
Alex Crichton said:
The main thing I think needs to keep working is rustc by default works on platforms missing the libraries (e.g. missing mingw compiler/objects), but I suspect everyone feels the same way about that :)
I'm happy to answer any questions.
Whether binaries/libs/objects from
self-contained directory are taken into account is controlled by crt_objects_fallback. So nothing really changes for end users yet, rustlib looks a bit cleaner with less irrelevant things laying next to Rust stuff.
This might require another MCP but the goal is to have heuristic for every affected target that can be overridden by currently unstable
I'm going to prepare heuristic for MinGW, @Vadim Petrochenkov was experimenting with musl. Would be great if somebody experienced with WASM could weight in.
Please ping me when this gets implemented, it is likely that xargo will need adjustment to keep working for those targets.