<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - Pathnames mangled under windows" href="https://bugs.freedesktop.org/show_bug.cgi?id=74559#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - Pathnames mangled under windows" href="https://bugs.freedesktop.org/show_bug.cgi?id=74559">bug 74559</a> from <a class="email" href="mailto:tomsies@mighty.co.za" title="Dirk <tomsies@mighty.co.za>"> Dirk</a> <pre>Yeah, I get your point also (with respect to stuff in fonts config other than the fonts and cache directory) Note that the patch does achieve a cache directory. The (unpatched) code aleady makes effort to get the executable directory in the event that dllMain is not invoked and then use that as a basis for fonts.conf aquisition. Problem is that this executable will whatever the "run" directory is at invokation i.e. equivalent to pwd. In the event of a static link, I dont know of a way to get back to the directory of the statically linked library from the executable? For example if the library sits in /usr/local/lib, and my statically linked executable sits in /opt/somestuff/bin, the closest I can come to finding a runtime directory will be /opt/somestuff/bin with (to my limited knowledege) no way of getting back to /usr/local/lib.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>