On 10/25/17 1:34 PM, Gregory Szorc wrote:
Also, due to ongoing work around Rust integration in the build system, it is dangerous to rely on manual `cargo` invocations to compile Rust because bypassing the build system (not using `mach build`) may not use the same set of RUSTFLAGS that direct `cargo` invocations do. Things were mostly in sync before. But this change and anticipated future changes will cause more drift. If you want the correct behavior, use `mach`.
Is something like "mach cargo-geckolib check" from within the servo/ directory still expected to work sanely?
In general, it would be good to have a way to do a "check" on Rust code rather than a full compile with code generation when all you want is to find out all the ways in which your code is going to fail to compile...
-Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
