Version: unknown (using KDE 3.4.3, Debian Package 4:3.4.3-2 (testing/unstable)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.13 creating a new qt-project does not ask for qt-version, thus creating qt3-code. one may change to qt4 in project->project options and give the qt-root-dir but it is ignored. project->project options->c++ specific ->code completion: code completion databases [add]-> kdevelop qt pcs importer [next] presents only and immutable "/usr/share/qt3", not the given qt-root-dir. building uses stupidly the qt-tools of qt3, not of the given qt-root-dir. defining QTDIR in project does not help.
Last time I checked debian unstable was still using KDevelop 3.2.2 We released 3.2.3 and 3.3.0 after that. You need KDevelop 3.3.0 to get Qt4 support. Please read the KDevelop website before posting this kind of bug report.
well, it _is_ 3.3.0. thought, the bugtracker would add the version of the program in question automatically -- but it's not done. got kdevelop 3.3.0 from ubuntu's breezy and compiled by myself.
Did you read the FAQ and searched the forum ?
yes.
No, the setting isn't ignored. It's not taken into consideration at all. The "Qt4 support" added in 3.3 is a patch to the C++ Class Wizard, adding support to create the correct looking include syntax when subclassing a Qt3 or Qt4 class. That's all. The build system support has in any case no business using a setting from the C++ support and will just call the Qt tools in $PATH (or so I assume). The C++ code completion database wizard is untouched and is unaware of this Qt4 setting. You are correct that it should be updated.
This is certainly confusing; choosing Qt4 should run qt4's qmake, not qt3's (which is logically in the PATH since kdevelop is in the PATH... mixing qt3 and qt4 binaries in the same environment isn't really a good idea, especially with kde3/kde4). Also this means setting things up by hand before launching kdevelop, not really intuitive.
As a stopgap measure, people who want to use kdevelop for developing Qt4 projects should launch this script instead of kdevelop: #!/bin/sh export QTDIR=$HOME/src/4/qt-copy export PATH=$QTDIR/bin:$PATH exec kdevelop $* (adjust the value of QTDIR of course). For kdevelop-3.4, the qt3-vs-qt4 option should be moved out of "C++ settings" and into whatever upper layer should have it :-) Thanks.
Yes. KDevelop should support Qt4. This report is still based on a misunderstanding about what the code attempts to do, so to call it a bug isn't really correct. Changing to wishlist and renaming.
I'm not sure it's a case to open new wish/bug, and it seems this issue is right place. Speaking about (current state) 3.4 svn branch. There is QT4 support. Great! Thanks! The problem appears when you want to add some QT module rather QtCore/QtGui. Let it be QtXml. Of course, I can directly add '-lQtXml' to qmake subproject libs. When I change subproject property "Release" to "Debug", I must remove '-lQtXml' and add '-lQtXml_debug'. I think, some kind of 'Use modules' (sub)dialog/form woud be more "QT-way". ______________ Thanks to KDevelop development team for the IDE!
Closing, everything is fixed in KDevelop3.4