Hi Eric, On 03.05.2005, at 15:19, Eric Hoch wrote:
No. Without patching OOo-freetype's makefile.mk freetype will never compile on MacOSX. So, on MacOSX the default is to use system's or rather X11's freetype.I chose to do it because I got a missing freetype header error in vcl. I'll
create an issue for
that once my Mac is fully workable again.
O.K. Let my try to get it correct. You use freetype2 2.1.4 and you get a missing freetype header in vcl. You use freetype 2.1.9 and you don't get a missing freetype2 header in vcl? Right? If so it sounds strange. Anyway, for now I have workaround for Darwinports freetype problem and that's what counts for me for the moment.
But while compiling vcl, the needed header wasn't found (although present in /usr/X11R6/include). Anyway, I thought maybe it's best to use as little from the system as possible to make OOo more self- contained, and so I am using OOo's freetype 2.1.4
Clear now? :)
Best regards, Florian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
