[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 814 in lilypond: warning-as-error should be enabled when compilin
From: |
codesite-noreply |
Subject: |
Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests |
Date: |
Fri, 17 Jul 2009 07:53:33 +0000 |
Status: Accepted
Owner: v.villenave
CC: pnorcks, john.mandereau, n.puttock
Labels: Type-Enhancement Priority-Medium Maintainability
New issue 814 by v.villenave: warning-as-error should be enabled when
compiling the regtests
http://code.google.com/p/lilypond/issues/detail?id=814
The new -dwarning-as-error option makes it easier to track warnings and
progerrors, which may improve the quality of LilyPond code in general,
particularly when it comes to regtests.
Some regtests intentionally emit warnings; we should carefully check these
particular ones and disable the option by adding:
#(ly:set-option 'warning-as-error #f)
Otherwise, warning-as-error should be enabled by default in the regtest
makefile. John has already sent a patch to do that:
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
Please refer to the discussion on
http://lists.gnu.org/archive/html/bug-lilypond/2009-07/msg00146.html
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests,
codesite-noreply <=