Re:Cargo: predictable dependency management
by SimonSapin on Friday May 06, 2016 @03:08AM
(#11642244)
Mach is what you interact with when doing stuff in Servo, but all the build-* sub-commands end up calling Cargo, which is what does the heavy lifting.
The typical `./mach build` command will download known-good versions of Rust Nightly and Cargo (unless that’s already done), call `cargo build` with some flags, then show a system notification when it’s done. That’s it.
Re:Cargo: predictable dependency management
by steveklabnik on Friday May 06, 2016 @12:01AM
(#11641609)
Servo relies on a specific version of Rust, and Mach helps with that.
Cargo isn't a general build system, it builds Rust code. I use Make to drive Cargo for my OS project, because I use nasm to build the asm and Cargo to build the Rust, for example.
If you look at the build step from github it looks like it's relying on mach also:
https://github.com/servo/servo#building
Shouldn't it instead be using cargo purely?