On 29-Jul-05, at 1:53 AM, Han-Wen Nienhuys wrote:
After poking around a bit, I realized the problem -- since I'm
building lilypond
myself in my home directory, of course the sytem-wide fontconfig
won't find
the lilypond fonts. I can point fontconfig at the fonts with
~/.fontconf , but then
I still need to update that file with the new version number.
This is red herring. LilyPond does
FcConfigAppFontAddDir
for its own font directories. I think you have a linking problem. Is
it dynamically linked? Try otool -L on the binary
spark:~/usr/pkg/lilypond/bin gperciva$ otool -L lilypond
lilypond:
/sw/lib/libintl.1.dylib (compatibility version 2.0.0, current
version 2.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 71.1.3)
/sw/lib/pango-ft219/lib/libpangoft2-1.0.0.dylib (compatibility
version 801.0.0, current version 801.1.0)
/sw/lib/pango-ft219/lib/libpango-1.0.0.dylib (compatibility
version 801.0.0, current version 801.1.0)
/sw/lib/libgobject-2.0.0.dylib (compatibility version 601.0.0,
current version 601.5.0)
/sw/lib/libgmodule-2.0.0.dylib (compatibility version 601.0.0,
current version 601.5.0)
/sw/lib/libglib-2.0.0.dylib (compatibility version 601.0.0,
current version 601.5.0)
/sw/lib/libiconv.2.dylib (compatibility version 5.0.0, current
version 5.0.0)
/sw/lib/fontconfig2/lib/libfontconfig.1.dylib (compatibility
version 2.0.0, current version 2.4.0)
/sw/lib/freetype219/lib/libfreetype.6.dylib (compatibility
version 10.0.0, current version 10.7.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current
version 1.0.0)
/sw/lib/libexpat.0.dylib (compatibility version 6.0.0, current
version 6.0.0)
/sw/lib/libguile.12.dylib (compatibility version 16.0.0,
current version 16.0.0)
/sw/lib/libguile-ltdl.1.dylib (compatibility version 2.0.0,
current version 2.0.0)
I don't know if this is good or bad...
To clarify further, I have fontconfig, pango, and whatnot[1] installed
via fink in /sw, owned
by root. I build lilypond as a user, and install it in
$HOME/usr/pkg/lilypond as a user.
If the LilyPond binary tells itself where the fonts are, then something
is wrong. If "make
install" is supposed to tell fontconfig where the fonts are, then
nothing is wrong -- the
install is running with user privs, and shouldn't be able to mess with
the root-installed
fontconfig stuff.
[1] apart from mftrace; that's installed as a user, since the mftrace
in fink for 10.3 is too
old.
Cheers,
- Graham
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
