James McKenzie wrote:
Something that I do have to point out is that freetype, a very
important
library for Wine is not shipped with XCode nor MacOSX. We have to include it.
Huh? On my 10.5.7 Leopard system, Wine was able to find FreeType -- with LD_LIBRARY_PATH guidance. And I have nothing but - MacOS (with iLife preinstalled) - (selected packages from) the Xcode install DVD and - XQuartz 2.3.3.2 installed on that box.
Did you install Apple's X11 before installing XQuartz, as the XQuartz site recommends?
Are you mislead by the following error message? ---- snip Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org Building font metrics. This may take some time... Font metrics: 0.0% done fixme:font:LFD_InitFontInfo DBCS fonts like '-daewoo-gothic-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0' are not working correctly now. ... ---- http://bugs.winehq.org/show_bug.cgi?id=17674#c4 I saw those on my first compile && make && ./wine winecfg
LD_LIBRARY_PATH=/usr/X11/lib ./wine notepad prevents those messages. Wine then starts up much faster (still slower than a slower Ubuntu box, some people suppose that is due to the many fonts) and does not re-generate font data for *every* subprocess ran inside Wine.
LD_LIBRARY_PATH=/usr/X11/lib is needed because libfreetype.* is there.
If you want, I'll try to identify (using pkgutil) what package installed /usr/X11/lib/libfreetype.*.
BTW, it would be nice if MacOS users could comment on a) my comment #4 to bug #17674 above or on b) my patch http://www.winehq.org/pipermail/wine-patches/2009-July/075290.html It was not included in Wine-1.1.25 perhaps because AJ awaits confirmations from other users?
Are there so many differences between MacOS systems (even Leopard only) or how to explain the different experience reports in this mailing list?
For completeness, Apple's libfreetype may have some bugs. E.g. some letters, esp. W and w look ugly in winecfg, while Kronenberg's version looks as crisp as a Linux one. I have not yet investigated this further, so it's too early for recommendations. For sure, it's not a matter of anti-aliasing (FontSmoothing): that works, the 'W' then gets shades of grey, but it's still not crisp, sharp, 1 pixel wide as on Linux.
BTW, I was about to rewrite the http://wiki.winehq.org/MacOSX/Installing wiki page, explaining how to build&compile when I faced that "censorship" issue.
Regards, Jorg Hohle