bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lilypond.pot polluted


From: Jean-Charles Malahieude
Subject: lilypond.pot polluted
Date: Sat, 03 Nov 2012 19:04:58 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121016 Thunderbird/16.0.1

Hi John and all,

I just noticed that, because the out of tree build, lilypond.pot gets
polluted by personal path, what does not happen with an "in tree" build.

e.g. we get, when "out of tree" :

#: parser.yy:174 parser.yy:188 /home/jcharles/GIT/Mentor/lily/parser.yy:174
#: /home/jcharles/GIT/Mentor/lily/parser.yy:188
msgid "Too much lookahead"
msgstr ""

#: parser.yy:466 parser.yy:736 parser.yy:803
#: /home/jcharles/GIT/Mentor/lily/parser.yy:466
#: /home/jcharles/GIT/Mentor/lily/parser.yy:736
#: /home/jcharles/GIT/Mentor/lily/parser.yy:803
msgid "bad expression type"
msgstr ""


instead of just :

#: parser.yy:174 parser.yy:188
msgid "Too much lookahead"
msgstr ""

#: parser.yy:466 parser.yy:736 parser.yy:803
msgid "bad expression type"
msgstr ""


As a matter of fact, only lily/lexer.ll and lily/parser.yy are concerned with the duplication. I suspect it comes from ALL_PO_SOURCES which gets defined in stepmake/stepmake/po-targets.make, but am not sure how to fix it. Once again, this does not occur when NOT building "out of tree" (you know I prefer a local clone).

Cheers,
Jean-Charles






reply via email to

[Prev in Thread] Current Thread [Next in Thread]