DescriptionIssue 2787: Sanitize usage of -DDEBUG, -DNDEBUG and assert
The compiler option -DNDEBUG is no longer being used: -DNDEBUG disables
the assert function, and assert is essentially stating that the program
cannot useful continue if the assertion is not met. -DNDEBUG is
basically an option for compiling an application to a limited amount of
ROM when aborting with a diagnostic is not preferable to crashing.
This is not the case for LilyPond. So expensive debugging options now
are enabled with -DDEBUG instead. At the current point of time, setting
this is still tied to the configure option --disable-optimising. It
might make sense to move this to a separate option --enable-testing or
similar, but that would require simultaneous changes to the Patchy
testing framework.
Patch Set 1 #Patch Set 2 : Add --enable-checking option, let it be implied by --disable-optimising for now #
MessagesTotal messages: 3
|