On Wednesday 15 April 2009 06:11:16 David Johnson wrote: > On Tuesday 14 April 2009 08:34:54 am David Naylor wrote: > > Yes, I had a look and found the problem. QMAKE_CFLAGS_X11 now gets > > included into QMAKE_CXXFLAGS. This is a problem since QMAKE_CFLAGS_X11 > > gets add QMAKE_CFLAGS_FONTCONFIG (from pkgconfig) that includes > > -I/usr/local/include. The culprit. There does not appear to be a proper > > away around this (i.e. get QMAKE_CFLAGS_X11 added to the end of > > QMAKE_CXXFLAGS *after* other includes have been added). > > I wonder why it is not a problem for me? In any case, the patch turns off > fontconfig support. Don't we need that for decent looking fonts?
It shouldn't turn off fontconfig support, it should force the script to use the default values (i.e. not use pkgconfig). That was the intent. Anyways, to fix it make sure QMAKE_CFLAGS_FONTCONFIG is assigned with "". > Hopefully I can take a look this weekend at more of this.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
