On Sun, Apr 27, 2008 at 10:33 PM, John Mandereau <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote: > > On Fri, 25 Apr 2008 23:12:26 +1000 > > "Joe Neeman" <[EMAIL PROTECTED]> wrote: > > > > > On Fri, Apr 25, 2008 at 10:57 PM, John Mandereau > > > <[EMAIL PROTECTED]> wrote: > > > > > > > Incomplete test-clean and web-clean can be cumbersome when you're > > > > working on C++ code, but it's very useful when you don't want to > > > > rebuild all lp-book snippets, e.g. when you edit the documentation > > > > or hack documentation building. > > > > > > If you don't want to rebuild all of the snippets, why do 'make > > > web-clean' in the first place? > > Because docs building is so complicated that it's quite hairy to write > makefiles, so that all portions of the docs that changed since last > build are actually rebuilt. I experienced that the best way testing > changes in doc building is cleaning all output and rebuilding from > scratch, although I'm generally not interested in rebuilding snippets. > > > > I agree; `make web-clean' should remove anything created by `make web'. > > In topdir/out/lybook-db, it's not possible to make a difference between > what was created by web or test make targets. However, I made web-clean > and test-clean erase topdir/out/lybook-db, which seems to be what most > people building Lily expect. Thanks!
_______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
