David Dawes wrote:
On Wed, Nov 19, 2003 at 07:47:04PM -0500, Ed Sweetman wrote:

Not sure if this is the place for bugs, in fact i really think it's [EMAIL PROTECTED] so i'll cc it to them too.


It might have been mentioned already but the cvs head is not up to date with freetype2 2.1.7 Many XFT and freetype related source and header files have #include <freetype/freetype.h> and other assorted headers which is not how you use libfreetype anymore. You're supposed to #include <ft2build.h> and then use macro includes for the various headers. The new version of freetype2 also appears to have broken compiling for lib/font/FreeType. I have no idea why there is a duplication of many headers in Xfree86's source tree and so far changing includes to be what they should be isn't fixing the these errors with expected headers missing and what not. Is nobody else seeing these errors?


Something like the attached patch should take care of most of it.
Let me know if it works.

Amongst some other complications, lib/font/FreeType has at least
one dependence on a header that isn't exported (ttobjs.h), so
building against an external version currently probably won't work
as expected.  Maybe that can be handled differently?

The patch attached should address the other parts of lib/font/FreeType.

David


Yea, most of this i'd already done. It seems that freetype2 2.1.7 does not install ttobjs.h and it borks the install of the services headers by not putting them in a services directory. Upon fixing that. I come across errors relating to the fact that headers with the same name as freetype2's appear in the X cvs tree. Such as ft2build.h It appears an old tree of freetype2 is in X which is really bothering me. Why is it there and why do any of the source files include it via path directly without any define anywhere to say not to use the system freetype2? I know it's using those files over the system ones because if i delete a common header i start getting build errors. This looks like either a serious design flaw or a bug. If i go through the trouble setting a truetype2 directory via host.cf it should use that and not the included xfree86 tree.

I cant build X now even with the patch because of me refusing to let the build use the local tree (removed it from extras). I cant find where you specify FTSOURCEDIR which apparently X needs (why?) to point to my current freetype2 build dir.

_______________________________________________
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86

Reply via email to