Am 11.10.2017 um 18:46 schrieb Federico Bruni:
Il giorno mer 11 ott 2017 alle 18:20, Malte Meyn <lilypond@xxxxxxxxxxxx>
ha scritto:
Am 10.10.2017 um 19:02 schrieb Jean-Charles Malahieude:
What about if you first build the binaries? I've noticed, when
working with a fresh clone, that the sequence is (from the top-dir
and a quadcore)
./autogen.sh
That was it. For building the binaries I ran autogen.sh with the
--noconfigure option. This works for building the binaries and the
docs but not for make check-translation.
Unlikely: you need to run ./configure before building the binary anyway.
Perhaps you checked out the translation branch after working on the
master branch, where maybe you worked on the build/ dir?
If I run ./autogen.sh --noconfigure from the root directory and then
../configure from the build directory, it’s not enough, you need
./configure from the root directory or ./autogen.sh without --noconfigure:
~/lilypond (translation=)$ rm -rf * # to clean all config things
~/lilypond (translation *=)$ git co -- * # to bring back the files known
to git
~/lilypond (translation=)$ ./autogen.sh --noconfigure &>/dev/null
~/lilypond (translation=)$ mkdir build
~/lilypond (translation=)$ cd build
~/lilypond/build (translation=)$ ../configure &>/dev/null
~/lilypond/build (translation=)$ cd ../Documentation/
~/lilypond/Documentation (translation=)$ make ISOLANG=de check-translation
make: /python/langdefs.py: Kommando nicht gefunden
make: /python/langdefs.py: Kommando nicht gefunden
../make/stepmake.make:130: /stepmake/omf-targets.make: Datei oder
Verzeichnis nicht gefunden
make: *** Keine Regel, um „/stepmake/omf-targets.make“ zu erstellen.
Schluss.
~/lilypond/Documentation (translation=)$ cd ..
~/lilypond (translation=)$ ./autogen.sh &>/dev/null
~/lilypond (translation=)$ cd Documentation/
~/lilypond/Documentation (translation=)$ make ISOLANG=de
check-translation >/dev/null # success
langdefs.py: warning: lilypond-doc gettext domain not found.
~/lilypond/Documentation (translation=)$