Hi, First my apologies for not being subscribed to this group. I _do_ check the archives on a regular basis though...
I have a little question that has been haunting me for the past few days: Summary: KDE3.0.4 (recompiled) lacks antialiasing support (in the GUI) when compiled against a recent CVS (19 nov 2002) of XFree86. What I found out so far: My X env supports RENDER & AA works with my current X (CVS) compilation (xterm -fa "andale" shows AA'd xterm). Even kfontinstall shows AA'd preview of the fonts!! (I switched on AA support in KDE/Kcontrol) I suspect I need working xft headers in order to have anti-aliased fonts in KDE? I assume the debian QT3 packages are compiled with -xft? ./configure decides to give up on xft because Xft.h refers to a file that can't be found. (But continues). Checking Xft.h reveals that it refers to freetype.h, which is available, not in the freetype dir but freetype2/freetype. Pointing to freetype2/freetype/freetype.h in Xft.h doesn't work, ./configure complains about not finding other files (turns off xft and continues). Moving freetype one level above (next to freetype2) results in a happy Xft.h in ./configure and included xft support. Compiling however fails on inconsistencies in multiple declarations of a function and the lack of others (originating from the found and accepted Xft.h). I remember reading that freetype is being turned upsidedown in this (4.3.0) release of XFree86 and things might not compile as you expect them. So I noticed. Question: should I stop and get some sleep since it will not work (soon) or is there a quick 'workaround' (like the one with the freetype dir I tried before)? Will Xft.h headers eventually work in 4.3.0, or is this a transition to a whole new approach of Xft? I see a Xft and Xft1 dirs in the CVS structure at the moment namely. Anyway, if someone could enlighten me a bit here, I'd be pleased... Regards, Martin van Es _______________________________________________ Render mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/render
