On Thu, May 11, 2017 at 5:15 PM, Jeff Muizelaar wrote:
> On Fri, Apr 14, 2017 at 10:46 AM, Nathan Froyd wrote:
>> 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
On Fri, Apr 14, 2017 at 10:46 AM, Nathan Froyd wrote:
> 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
Since the subject and the body disagree on what the actual option is
called, let me be clear - the correct option is --enable-rust-debug.
Cheers,
Josh
On 2017-04-15 12:46 AM, Nathan Froyd wrote:
Bug 1353810, recently merged to central, adds a new configure option
--enable-debug-rust
This is awesome - thanks Nathan!
On Fri, Apr 14, 2017 at 10:46 PM, Nathan Froyd <nfr...@mozilla.com> wrote:
> 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-fr
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
5 matches
Mail list logo