Mats Bengtsson <[EMAIL PROTECTED]> writes:
> This is nonsence. If the TEXMF variable doesn't include
> the default teTeX texmf tree, TeX or LaTeX won't be able
> to find any of the standard package files.
Oops. So, make that:
TEXMF="{$(pwd)/lilypond/share/lilypond/<version>, $(kpsexpand \$TEXMF)}"
> Use a setting similar to the one in buildscripts/out/lilypond-profile
> instead.
Yes, but I just wanted to mention that (wrong) TEXINPUTS, TFMFONTS,
MFINPUTS, override a (correct) TEXMF and still break things.
> Also, since the build directory doesn't match the
> standard TeX directory structure (see `texdoc tds`),
> tex/latex won't find any of the font files or other
> necessary files.
How is that? .62/latest CVS should create a valid tds in the build
directory, but I'm not a guru at this (as my prev post also shows).
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
