One thing that would clear up a lot of confusion for me is a
collection of concise "cycles" for different development
tasks. Something like this, but correct my mistakes,
because I'm confused:
Documentation editor's edit/compile cycle:
Initial:
make
make doc
Cycle:
[edit source files]
make <-- is this needed?
make doc
Reset:
make doc-clean
Developer's edit/install cycle:
Initial:
make
make install
Cycle:
[edit source files]
make <-- is this needed?
make install
Reset:
make uninstall
Developer's edit/test cycle:
Initial:
make
make test-baseline
[edit source files]
make
make check
Cycle:
[edit source files]
make
make test-redo
make test-clean <-- really? (from CG 3.1.5)
make check
Reset:
??
Also, are there any other common task cycles to mention?
This would be really helpful!
Thanks.
- Mark
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
