On Tue, May 03, 2011 at 02:15:39AM +0200, Don Simons wrote:
> They start with what happens when I try to compile mtxdoc according to Dirk's
> instructions. I didn't think makefiles had a place in the Windows command
> window, but to my surprise, when I unzipped mtxD060.zip and blindly typed
> 
> make dvitarget && make config
> 
> as instructed, I did not get nothing. 

I don't know what sort of makefile your make.exe expects, but I'd be 
quite surprised if it works on any version of Windows except when you
have cygwin installed.

> ln -sf make-dvi make-target

I'm assuming that the typical user likes either DVI files or PDF files.
This step links your default choice to make-target.  You could also
copy make-dvi or make-pdf to make-target.  It will be included into the 
main Makefile, specifying: 
    which latex to run, 
    how to concatenate output,
    how to make .ps files.

> 
> Verry interesting, but from this point on I'm clueless on this path.
> However, just for laughs I will try to compile the document using commands I
> do know about such as 
> 
> for %a in (*.mtx) do prepmx %a
> 
This won't work.  Most of the M-Tx code is split up into two or more
files, only one of which is included into the document.  You need to
concatenate the two parts.  The rules to make xxx.mtx are:
    1. If xxx.mta and xxx.mtb both exist, concatenate them.
    2. For melisma1.mtx etc, concatenate melisma.mta with melisma1.mtb etc.
    3. For netsoos.mtx, concate netsoos.mta with all the netsoos&.mtb files.

> At the moment the next mystery is how to similarly send just the basenames as
> arguments to the musixflx command. Or maybe it'll work on *.mx1 ?
> 
musixlfx is run on mtxdoc, not on the separate files.

Actually, GNU Makefiles are not too hard to read, if you know the
following:
    1. A line that looks like an assignment statement defines an
        abbreviation later referred to by $(...).
    2. Backslash at the end joins physical lines into one logical line.
    3. "a: b" means: to make "a", check whether everything in "b" exists 
        and whether any is newer than the current "a".  The tabbed lines 
        after that give the commands that will be executed in that case.

Dirk

-------------------------------
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

Reply via email to