Bug 1353810, recently merged to central, adds a new configure option --enable-debug-rust. This option enables compiling the Rust code in-tree with debug-friendly settings (no optimization, multiple codegen units for faster compiles, etc. etc.) even if you are compiling with --disable-debug. The intended use is in a mozconfig thusly:
ac_add_options --enable-optimize ac_add_options --disable-debug ac_add_options --enable-rust-debug With these options, you get a browser that runs quickly (i.e. no DEBUG assertions in C++ code), but still lets you debug the Rust code you might be working on, ideally with faster compile times than you might get otherwise. --enable-debug implies --enable-debug-rust, of course. This configure option is not represented in any of our automation configs and did require a few strategically placed #ifdef MOZ_RUST_DEBUG, so it's entirely possible that changes to code on the C++/Rust boundary will break compiling with this option. Please be careful. If you have ideas on how this config option could be improved, or ideas on how to improve our developer ergonomics around Rust compilation generally, please file a bug in Core :: Build Config. Thanks, -Nathan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
