<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - fonts.conf.in update for Windows cross-compiling"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69836">69836</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>fontconfig-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>fonts.conf.in update for Windows cross-compiling
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>freedesktop@behdad.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jehan@zemarmot.net
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>conf
</td>
</tr>
<tr>
<th>Product</th>
<td>fontconfig
</td>
</tr></table>
<p>
<div>
<pre>Hi,
I am a GIMP developer. We had a problem when cross-compiling GIMP for Windows
(<a href="https://bugzilla.gnome.org/show_bug.cgi?id=708110">https://bugzilla.gnome.org/show_bug.cgi?id=708110</a>).
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:
<a href="https://git.gnome.org/browse/gimp/tree/build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch">https://git.gnome.org/browse/gimp/tree/build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch</a>
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?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>