Le mercredi 20 février 2008 à 00:26 -0800, Graham Percival a écrit : > On Wed, 20 Feb 2008 08:54:18 +0100 > John Mandereau <[EMAIL PROTECTED]> wrote: > > Is this the whole end of the log? This looks very strange. > > It's the end. I'm sending you a complete log privately.
Oh yes, I had not figured out immediately that you made web in Documentation/user. > cd Documentation/user/ > make ... web > ls out-www/*.html > % show only the -big-page.html files; no index.html or smaller html > files. That's strange: I got the same warnings as you for missing Info images, but all PDFs and both big and splitted HTML manuals were built successfully. I'm puzzled that I thought I had previously managed to build and install Info docs with images, whereas this no longer works. I tested with GUB linux-x86 2.11.40 EXTERNAL_BINARY too, but the problem is exactly the same as with the classic build. I've played further with docs makefiles, issued both non-clean and clean builds, and it works for me. I hope it'll work for you too :-) > >From the top source dir, I did > rm -rf * > git reset --hard > ./autogen.sh > cp GNUmakefile.in GNUmakefile > make -C python > cd Documentation/user/ > make ... web > > I don't know how to get it any cleaner than that. With well-written docs makefiles, I expect to a) be able to rebuild only what's needed when I edit some .itely or .tely files, without having to clean everything (even not delete .html or .pdf files) -- that's the purpose of make, btw. b) not rebuild each time targets that are already up-to-date; that's not always doable in a reasonable way, e.g. symlinking .pngs from translated docs to Documentation/user/out-www, or the final step www_post.py. The former makefiles for English docs did not achieve a), whereas makefiles for translated docs did not achieve b). The purpose of my current playing with makefiles is to have both a) and b) for all docs. With latest changes I've made and a lot of testing, I think I've done a) for all docs, b) for docs in English, and almost b) for translated docs [1], and of course I hope clean builds are successful, which is the least we can expect from makefiles :-) Please report any problems as usual. [1] lilypond-book is always running, even if there is no target to update, and symlinks are always remade, but it's much better than before (lilypond-book, makeinfo and texi2pdf were all called unconditionnally at every 'make web' invocation before), and excessive rebuilding is not harmful in translated docs (it would be in docs in English, e.g. when installing Info docs as root). Cheers, John _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
