On Friday 04 February 2011 21:14:19 David C. Rankin wrote:
On 02/03/2011 10:29 PM, David C. Rankin wrote:
<snip>
But even with these variables, the build grabs QtCore regardless.
Serghei,
Looking closer, the kdebase admin/acinclude.m4.in may be part of the problem. It seems to check for kde4 first and then sets QTDIR to qt4 if found before checking for kde3:
acinclude.m4.in is not related in any way with cmake
[ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o cd /dat_e/david/bld/trinity/kdebase/src/kicker/libkicker && /usr/bin/c++ -Dkickermain_shared_EXPORTS -DHAVE_CONFIG_H -DUSE_QT3 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -march=x86-64 -mtune=generic -O2 -pipe
Ensure that kickerSettings.cpp is not generated by Qt4 uic. To avoid these stange problems, I suggest to use a virtual machine or chroot with clean setup.