[Fontconfig-bugs] [Bug 69836] New: fonts.conf.in update for Windows cross-compiling
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 26 00:12:08 PDT 2013
https://bugs.freedesktop.org/show_bug.cgi?id=69836
Priority: medium
Bug ID: 69836
Assignee: fontconfig-bugs at lists.freedesktop.org
Summary: fonts.conf.in update for Windows cross-compiling
QA Contact: freedesktop at behdad.org
Severity: normal
Classification: Unclassified
OS: Windows (All)
Reporter: jehan at zemarmot.net
Hardware: Other
Status: NEW
Version: unspecified
Component: conf
Product: fontconfig
Hi,
I am a GIMP developer. We had a problem when cross-compiling GIMP for Windows
(https://bugzilla.gnome.org/show_bug.cgi?id=708110).
This was just a configuration issue, with the configuration files in conf.d/*
being inaccessible because the path set by the autotools in fonts.conf during
compilation were obviously different once the tree was moved over from a Unix
to a Windows system.
This simple patch would fix it for us:
https://git.gnome.org/browse/gimp/tree/build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch
Since it is a configuration issue, it could be argued that it is not a bug.
Still I feel that cross-compiling fontconfig would be quite common. And if our
tree for GIMP has a patch for fontconfig, it may mean that it would be worth
updating upstream too, no? :-)
I would propose 2 changes:
1/ Replace @CONFIGDIR@ by "conf.d", and not a full path, only when
cross-compiling for Windows like in our patch.
2/ and/or having a warning message when an <include>d directory set in
fonts.conf does not exist, so that at least there is some feedback from the
software to understand easily the issue (otherwise it was hard to diagnose what
was going wrong). :-)
Does it make sense?
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20130926/5217f1b9/attachment.html>
More information about the Fontconfig-bugs
mailing list