Agreed. A large project (at least a project with a large number of files and variations) is best handled with makefiles and with some sort of source code control. There are lots of free tools. Google is your friend. For example, search for something like "makefile howto linux" and you'll find lots of guidance. And Source Code Control can help keep track of history, allowing such actions as backing out changes to an earlier version that actually worked.
Joe Mark Knoop wrote: > At 17:32 on 04 Jan 2010, Federico Bruni wrote: > >> Il 04/01/2010 14:14, James Lowe ha scritto: >> >>> Can you use the \tag option here? To set a variable that you could >>> then 'filter' in the book.ly? >>> >> this could have been a good idea, but I think I can't apply it in my >> situation >> > > What about using a Makefile for the project which preprocesses the > included files (with sed for example) to comment out the midi block. It > could then uncomment the block again after compilation. > > _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
