On Monday 19 May 2008, Matthias Kretz wrote: > > You mean the line under MOC_INCLUDES? Yes, it contains the path to > > kdebase/workspace/libs, but this doesn't change the fact that the > > installed one is taken and not the one from the kdebase source dir. > > My question was not whether it contains that path but whether the > order in that file is correct or not. Because that tells you whether > the error is in automoc or somewhere else. (i.e. correct order in > that file => error in automoc4; incorrect order in the file => error > in cmake scripts)
See here:
MOC_INCLUDES:
/data/development/sources/kde-trunk/kdebase;/data/development/build/kde-
trunk/kdebase;/opt/kde4/include;/opt/kde4/include/KDE;/opt/qt4
/include/phonon;/opt/qt4/include/QtXmlPatterns;/opt/qt4/include/QtWebKit;/opt/qt4/include/QtHelp;/opt/qt4/include/QtAssistant;/opt/qt4
/include/QtDBus;/opt/qt4/include/QtTest;/opt/qt4/include/QtUiTools;/opt/qt4/include/QtScript;/opt/qt4/include/QtSvg;/opt/qt4/include/Q
tXml;/opt/qt4/include/QtSql;/opt/qt4/include/QtOpenGL;/opt/qt4/include/QtNetwork;/opt/qt4/include/QtDesigner;/opt/qt4/include/Qt3Suppo
rt;/opt/qt4/include/QtGui;/opt/qt4/include/QtCore;/opt/qt4/include/Qt;/opt/qt4/mkspecs/default;/opt/qt4/include;/usr/include;/data/dev
elopment/build/kde-
trunk/kdebase/workspace;/data/development/sources/kde-
trunk/kdebase/workspace/kdm;/data/development/sources/kde-tru
nk/kdebase/workspace/libs;/data/development/sources/kde-
trunk/kdebase/workspace/libs/kworkspace;/usr/include/NetworkManager;/usr/inclu
de/glib-2.0;/usr/lib64/glib-2.0/include;/data/development/sources/kde-
trunk/kdebase/workspace/solid/networkmanager-0.7/dbus
So it has both /opt/kde4/include (my trunk installation) and
/usr/include (the system dir where KDE 4.0 is installed) before
/data/development/sources/kde-trunk/kdebase/workspace/libs
(where the updated .h files are and those should be used).
I even modified my CMakeList.txt to have kdebase/workspace/libs as the
first include dir:
include_directories(
${CMAKE_SOURCE_DIR}/workspace/libs
${NETWORKMANAGER_INCLUDE_DIRS}
${NM-UTIL_INCLUDE_DIRS}
${CMAKE_CURRENT_SOURCE_DIR}/dbus
${CMAKE_CURRENT_BUILD_DIR}
)
>
> > Just lurk a little on #kde-devel and you will see how many run into
> > this problem.
>
> That doesn't help to find the cause either.
I was just pointing that this problem is far from being specific to my
system.
Andras
--
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
