[dev-servo] New build requirements for gecko-media

https://github.com/servo/servo/pull/19152/ finally merged, and it imposes some new requirements for completing a build of Servo. The process of making this work on TravisCI and our own CI builders was complex, so the full set of new requirements is not totally clear. Please file issues if your

Re: [dev-servo] RFC: Require rustup.rs to build Servo with mach

We can explicitly call `cargo +stable build` for geckolib, and have a min version check in mach. We'll only get the rust-toolchain file pinning for one of the two and will have to build some mach stuff for the other, but it will be considerably simpler than what we have right now. I think we shou

Re: [dev-servo] RFC: Require rustup.rs to build Servo with mach

I'm all for it, though I seem to recall there was some issue about needing two versions of Rust? How will we support the two different pinned versions (one for ./mach build and one for ./mach build-geckolib)? jack. On Tue, Nov 14, 2017 at 3:41 AM, Simon Sapin wrote: > In https://github.com/servo

[dev-servo] RFC: Require rustup.rs to build Servo with mach

In https://github.com/servo/servo/issues/11361 we’ve discussed using rustup.rs to bootstrap Rust and Cargo. With https://github.com/servo/servo/pull/19213 landing soon, I think the last blocker is resolved. One proposal has been to use rustup when available, and fall back to our existing mec