4 ms·
This article purports that Servo relies solely on Cargo for the build step. If you look at the build step from github it looks like it's relying on mach also:
by cetra3 10y ago
This article purports that Servo relies solely on Cargo for the build step.
If you look at the build step from github it looks like it's relying on mach also:
https://github.com/servo/servo#building https://github.com/servo/servo#building
Shouldn't it instead be using cargo purely?
- steveklabnik 10y agoServo 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.
- SimonSapin 10y agoMach 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.