Comment #12 on issue 1526 by julien.r...@gmail.com: Building only English docs
http://code.google.com/p/lilypond/issues/detail?id=1526
If I'm picking my answer there would be no patch because I would stick to the `make this-file' idiom. Special targets like `make doc' are available and they make sense to build a bunch of files, but what you're suggesting is a special target for every single file. I think that's overkill when 1) the targets are there for single files, they are the file's name, and 2) when you have proper dependencies and you edit a single file, the build system takes care to build just that single file with a standard `make', so you only ever need one long compilation on a clean tree and one command to remember for updating your tree. Add 3) your build system is complicated enough, with options and targets that nobody knows what there for, we should be removing complexity not increasing it.
For me the idiosyncrasies that render the standard make workflow unintuitive in the lilypond build are in my opinion the `out=www' part and the `make local-doc' instead of `make doc'. Thus what I secretly would like is: 1) Get rid of out and out-www dirs. Just mirror the directory tree of the src dir in the build dir. Or if you really insist on output subdirs, at least keep only one of them. 2) Have `make doc' build only the English docs. Not the translations, not the regressions, and not the website. Those should be different targets. That was something really unintuitive to me, that forced me to look for and find the `make local-doc' thing.
In the end I might strike you with such a patch and see what kind of complaints it gets.
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
