lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: blocking midi output of included files


From: Reinhold Kainhofer
Subject: Re: blocking midi output of included files
Date: Tue, 5 Jan 2010 17:46:07 +0100
User-agent: KMail/1.12.2 (Linux/2.6.31-15-generic; KDE/4.3.2; i686; ; )

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Dienstag, 5. Januar 2010 16:56:54 schrieb Mark Knoop:
> At 12:40 on 05 Jan 2010, Reinhold Kainhofer wrote:
> > Am Dienstag, 5. Januar 2010 11:10:07 schrieb Mark Knoop:
> > > 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.
> >
> > This results in all files always being rebuilt, since they are
> > changed. Not what a Makefile is for...
> 
> No, not unless you had set the included files' resultant pdfs as
> dependencies of the book file - and why would you do that?

Okay, to be more specific: The default target (typically "all") will now 
always detect that changes occurred (which is true, but they are not really 
desired changes) and thus always rebuild everything if you invoke make without 
a particular target.

In other words, to prevent make from rebuilding everything, you now always 
have to give an explicit target file to be built.

That situation is even worse if you want to modify one song and rebuild the 
book as well as the song... You can either manually give make the list of 
files that needs recompiling (i.e. you need to know the file names of the 
output files of all the really changes songs, plus the book; which totally 
defeats the dependence checking of make) or make will recompile all songs, 
even those that have not been changed by you...

Either way, for huge projects (and this issue of unwanted midi files is only 
an issue for huge projects) neither option is really compelling...

Cheers,
Reinhold


- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFLQ2zPTqjEwhXvPN0RAq2sAKCDCiLx44AVweTW5LC5OEawBtnmVwCcDm+C
s+WZlG71ZBbfXMgIYNfTHgA=
=5VMY
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]