On Mon, May 17, 2004 at 08:46:37AM +0100, Angus Leeming wrote: > Ling Li wrote: > > > Forgot to mention: Currently I "--disable-debug > > --disable-assertions" in making the 1.4.0cvs packages. If I remember > > correctly (since I disabled them long time ago), the reason to > > --disable-debug is that the package size is way too big with debug > > info, and the reason to --disable-assertions is that some assertions > > are too strict (without them LyX still works). But disabling them > > might be inappropriate if the purpose is to get users' feedback. > > Please let me know what compiling options should be used. > > It seems to me that getting the adventurous to use the cvs version > without debug info won't be very useful. "I get a core dump" doesn't > help much. So, I'd suggest that you should turn off optimization and > turn on debugging. > > Ditto with the assertions. Assertions are triggered by a logic fault. > We want them to abort because we want to write the code correctly.
I think the assertions are pretty important. And I haven't seen too many bogus asserts triggered lately. Andre'
