Hi, As of yesterday, LilyPond has a new -d option called
-dwarning-as-error Eventually, we want to use this option when compiling the regression tests; it will turn every "warning" or "programming error" into a real "error", causing the compile process to fail. This will be a "stress test" for the regression tests, since we don't want our regression tests emitting warnings or programming errors unintentionally. *** The following steps need to be taken for this to happen: 1.) Disable the option for every regression test that *intentionally* emits warnings or programming errors: #(ly:set-option 'warning-as-error #f) 2.) Fix the regression tests that are supposed to compile without any warnings or programming errors. (This is the long-term project) 3.) Enable -dwarning-as-error in the regtest makefile. John already posted a patch for this: diff --git a/input/regression/GNUmakefile b/input/regression/GNUmakefile index 753d483..f1a8179 100644 --- a/input/regression/GNUmakefile +++ b/input/regression/GNUmakefile @@ -7,3 +7,5 @@ include $(depth)/make/stepmake.make TITLE=LilyPond Regression Tests SUBDIRS=musicxml + +LILYPOND_BOOK_LILYPOND_FLAGS += -dwarning-as-error Step 3.) might be a few years away, but IMO, this should be on the tracker so it is not lost. Thanks, Patrick _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
