They are indeed! We’ve got builders for Linux, OSX, MSVC, and MinGW all testing rustbuild. Additionally, all cross-compiled nightlies (e.g. ARM Linux, FreeBSD, etc) are all produced by rustbuild.
And yes we’ll of course not just remove the makefiles one day, I should have been more clear on this! My current plan is along the lines of:
- For one cycle, discourage use of the makefiles, encourage developers to use rustbuild and add features to it
- For the next cycle, message out deprecation of the makefiles. Switch bots to using rustbuild by default and leave a bot or two testing the makefiles
- For the next cycle, delete the makefiles.
I’m hoping that gives everyone enough of a warning period to switch off the makefiles, and it primarily should affect developers as the external interface of rustbuild is the same (
make still works)
Yes this is something we’ll have to solve, but it’s always been a problem trying to deal with Cargo, I’m sure we’ll come to a reasonable solution.
If you mean from the perspective of the bootstrap happening as a result of a literal
cargo build, we’ll likely never enable that. If you mean in terms of
cargo actually being used to lazily compile libstd, that’s farther out and out of the scope of this thread unfortunately.
I’m always willing to chat about Cargo and Rust! Can at least say hi and see what’s up
We’ve got some fun vendoring-style features in the Cargo pipeline which I suspect will solve this issue as well. Note that I don’t want to derail this thread too much though as it’s centered around features in rustbuild. Would you mind opening up an issue to track the progress of this so we can continue the discussion there?