Next: Testing LilyPond, Previous: Building LilyPond, Up: Compiling from source
The documentation can be built locally without compiling lilypond from scratch.
From a fresh git checkout, do
./autogen.sh % ignore any warning messages cp GNUmakefile.in GNUmakefile make -C python nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond web % change the lilypond directory as appropriate
Please note that this may break sometimes – for example, if a new feature is added with a test file in input/regression, even the latest unstable Lily will fail to build the docs.
You may build the manual ( Documentation/user/ ) without building all the input/* stuff.
You may also need to create a script for pngtopnm and
pnmtopng
. On Linux, I use this:
export LD_LIBRARY_PATH=/usr/lib exec /usr/bin/pngtopnm "$@"
On OSX, I use this:
export DYLD_LIBRARY_PATH=/sw/lib exec /sw/bin/pngtopnm "$@"
In order to force make to build a complete manual (this does not rebuild all examples, only things which are changed), I recommend writing a script like this:
### run from Documentation/user/ # possibly required on OSX and/or old texinfo # ulimit -n 4096 if [ -e out-www/lilypond.texi ]; then rm out-www/lilypond.* ; fi; if [ -e out-www/lilypond-program.texi ]; then rm out-www/lilypond-program.* ; fi; if [ -e out-www/lilypond-learning.texi ]; then rm out-www/lilypond-learning.* ; fi; nice make LILYPOND_EXTERNAL_BINARY=~/usr/bin/lilypond web
To rebuild the complete HTML docs, run the above script from the
Documentation/user/ directory, then run the final line (the
nice make
) from the top source dir.
Next: Testing LilyPond, Previous: Building LilyPond, Up: Compiling from source
Cette page documente LilyPond-2.11.40 (branche de développement).
Rapportez toute anomalie en français à lilypond-user-fr@gnu.org ou en anglais à http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs
Vos suggestions à propos de la documentation sont les bienvenues.