Re: lilypond does *not* need metafont

[Reinhold Kainhofer]

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

Am Dienstag, 26. August 2008 schrieb Patrick McCarty:
> On Tue, Aug 26, 2008 at 07:58:19AM +0200, Werner LEMBERG wrote:
> > lilypond needs metapost, not metafont, for building the fonts!  The
> > binary is normally called `mpost' or `mp'.
>
> Hi Werner,
>
> Are you sure about this?  Looking at one of my `make all' logs, the
> following two lines appear, once for each .mf file (of course with
> feta13.mf, etc.):
>
> MFINPUTS=. mf-nowin -progname=mf "\mode:=ljfour; nonstopmode; input
> feta11.mf;" This is METAFONT, Version 2.71828 (Web2C 7.5.6)
>
> This all happens before any occurrence of `mpost'.

Also, we check for the mf-nowin, mf, mfw or mfont binaries in the configure 
step and exist if it doesn't exists, so it is indeed a build-time dependency 
of lilypond.

Cheers,
Reinhold


- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFItGkFTqjEwhXvPN0RAsZZAJ9TMyE5Hbrv1N6nd2c+WsEUOvuABQCgs9We
c59j2xHR1om2xtS+4KsTBxU=
=NgAZ
-----END PGP SIGNATURE-----