On Tue, Nov 10, 2009 at 12:27:51PM +0100, John Mandereau wrote: > Le samedi 07 novembre 2009 à 19:26 +0000, Graham Percival a écrit : > > I've got waf buliding contributor .html and .pdf in the dev/gperciva > > branch. I was pleasantly surprised to discover that waf supported a > > --targets= command-line, so we can specific an individual manual to > > build. I'm less happy that this appears to ignore the "after=foo" > > check, so none of the dependencies are checked. > > Please ignore my other reply on this technical point, which is > inaccurate. IIUC, dependencies should not be specified with 'after' > parameter, but a scanner that can be easily written reusing the one for > TeX should find dependencies, then Waf should find either the > dependencies as source files or output files produced by other tasks.
waf book, chapter 5, Task execution order. Ways to control the order of tasks: - task groups - precedence constraints (before= after=) - file extension production (ext_in= ext_out=) - task1.set_run_after(task2) In the next page, it appears that "dependencies" in waf-language are source files required for the task. Yes, we might want to do some kind of scanner for dependencies, but to say "run this rule before that rule" -- such as "generate version.itexi, by running the rule cunning named version.itexi" -- I think the easiest thing is to use "after" or having a task group. (actually, I must admit that task groups are looking appealing) - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
