John Mandereau <john.mander...@gmail.com> writes: > Jan Nieuwenhuizen a écrit : >> Good points, everything should be fixed. Improvements could be >> >> * add toplevel info and install-info targets that redirect to >> Documentation/user >> > ..and input/lsr too. I added toplevel info and intall-info target.
No, you didn't. At least a freshly fetched lilypond copy has only (according to bash programmable completion) the targets install-help2man install-info-WWW install-WWW make help offers -e Makefile for LilyPond 2.13.0 Usage: make [VARIABLE=value]... [TARGET] Targets specific to current directory: -e config rerun configure dist roll tarball: ././out/lilypond-2.13.0.tar.gz distclean also remove configure output doc update all documentation (without images) info build Info documentation with images info-install install Info documentation with images cvs-clean also remove out directories and generated files maintainerclean also remove distributed generated files po make new translation Portable Object database po-replace do po-update and replace catalogs with msgmerged versions po-update update translation Portable Object database web-install * install website documentation in (webdir=/usr/local/share/doc/lilypond/html) and Info documentation with images web-uninstall * remove installed documentation with images Some more targets are available for testing changes: test-baseline check test-redo test-clean For more information on these targets, see Testing LilyPond in Application Usage documentation. -e Generic targets: all * update everything except website documentation clean * remove all generated stuff in ./out bin-clean * same as clean, except that mf/out is preserved default same as the empty target exe update all executables help this help install * install programs and data (prefix=/usr/local) uninstall* uninstall programs and data lib update all libraries web * update website in directory `out-www' web-clean * clean `out-www' directory TAGS generate tagfiles `make' may be invoked from any subdirectory. Note that all commands marked with a star (*) recurse into subdirectories; prepend `local-' to restrict operation to the current directory. Example: `local-clean'. In short: there is no install-info target. make install bombs out, anyway: (/usr/bin/python /home/tmp/lilypond/stepmake/bin/install.py -c -d /usr/local/share/lilypond/2.13.0/fonts/otf/ || true) && /usr/bin/python /home/tmp/lilypond/stepmake/bin/install.py -c -c -m 644 ./out/emmentaler-11.otf ./out/emmentaler-13.otf ./out/emmentaler-14.otf ./out/emmentaler-16.otf ./out/emmentaler-18.otf ./out/emmentaler-20.otf ./out/emmentaler-23.otf ./out/emmentaler-26.otf ./out/aybabtu.otf ./out/CenturySchL-Ital.otf ./out/CenturySchL-BoldItal.otf ./out/CenturySchL-Roma.otf ./out/CenturySchL-Bold.otf /usr/local/share/lilypond/2.13.0/fonts/otf/ && (/usr/bin/python /home/tmp/lilypond/stepmake/bin/install.py -c -d /usr/local/share/lilypond/2.13.0/fonts/svg/ || true) && /usr/bin/python /home/tmp/lilypond/stepmake/bin/install.py -c -c -m 644 ./out/emmentaler-11.svg ./out/emmentaler-13.svg ./out/emmentaler-14.svg ./out/emmentaler-16.svg ./out/emmentaler-18.svg ./out/emmentaler-20.svg ./out/emmentaler-23.svg ./out/emmentaler-26.svg ./out/aybabtu.svg /usr/local/share/lilypond/2.13.0/fonts/svg/ && (/usr/bin/python /home/tmp/lilypond/stepmake/bin/install.py -c -d /usr/local/share/lilypond/2.13.0/fonts/type1/ || true) && /usr/bin/python /home/tmp/lilypond/stepmake/bin/install.py -c -c -m 644 ./out/feta11.pfb ./out/feta13.pfb ./out/feta14.pfb ./out/feta16.pfb ./out/feta18.pfb ./out/feta20.pfb ./out/feta23.pfb ./out/feta26.pfb ./out/feta-braces-a.pfb ./out/feta-braces-b.pfb ./out/feta-braces-c.pfb ./out/feta-braces-d.pfb ./out/feta-braces-e.pfb ./out/feta-braces-f.pfb ./out/feta-braces-g.pfb ./out/feta-braces-h.pfb ./out/feta-braces-i.pfb ./out/feta-alphabet11.pfb ./out/feta-alphabet13.pfb ./out/feta-alphabet14.pfb ./out/feta-alphabet16.pfb ./out/feta-alphabet18.pfb ./out/feta-alphabet20.pfb ./out/feta-alphabet23.pfb ./out/feta-alphabet26.pfb ./out/parmesan11.pfb ./out/parmesan13.pfb ./out/parmesan14.pfb ./out/parmesan16.pfb ./out/parmesan18.pfb ./out/parmesan20.pfb ./out/parmesan23.pfb ./out/parmesan26.pfb /usr/local/share/lilypond/2.13.0/fonts/type1/ && true Traceback (most recent call last): File "/home/tmp/lilypond/stepmake/bin/install.py", line 78, in <module> shutil.copy2 (f, dest) File "/usr/lib/python2.5/shutil.py", line 96, in copy2 copyfile(src, dst) File "/usr/lib/python2.5/shutil.py", line 51, in copyfile fsrc = open(src, 'rb') IOError: [Errno 2] No such file or directory: './out/CenturySchL-Ital.otf' make[1]: *** [local-install-outfiles] Error 1 make[1]: Leaving directory `/usr/local/tmp/lilypond/mf' make: *** [install] Error 2 d...@lola:/home/tmp/lilypond$ I really have no idea how people supposedly cope with that sort of thing. As it stands, the most basic targets just don't work at all and/or need parameters one could not possibly guess and/or are hidden away into some subdirectory make targets one cannot fathom and/or require running some other unnoticeable dependencies first. It might be nice if some developers made it into a habit to try building from a freshly checked out tree from time to time without reverting to their secret knowledge. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel