KDevelop 0.4 + Qt2.00; is it possible?

Bernd Gehrmann bernd at physik.hu-berlin.de
Mon Jul 19 13:09:36 BST 1999

On Mon, 19 Jul 1999, Arvid Nilsson wrote:

> Hi there!
> (Newbie alert)
> My question: I would like to be able to develop for qt2 in kdevelop. Can I
> somehow start with making a new normal qt project in the app wizard, and then
> change some settings to use my qt2 headers? I really don't have a clue about how
> to accomplish this. I also have to link against the qt2 libs somehow
> - I guess this involves the project/options/linker options/additional libraries
> text box somehow, but I'm not sure what to write there.
> I have both qt1.44 and qt2.00 installed now, and there seems to be no
> conflict.
> I'm using kde 1.1.1 with kdevelop 0.4. I have both qt1g and qt2 installed.
> Everything is installed with the debian packages from Ivan E. Moore II
> (kde.tdyc.com/Debian).

It all depends on whether you want to develop for Qt 1 _and_ Qt 2
or only one of them. In the first case, things are quite complicated.
In the latter case, things are roughly as follows: The qt1/qt2 packages
only contain the shared libraries. Header files are in separate
packages qt1g-dev (or similar). That's certainly the case on Debian,
and to the best of my knowledge also for RedHat. The header files are
installed under /usr/include/whatever and should be found by the
configure script (if you use a autoconf/automake setup). 

On the linker side: If you give the linker a command line option
'-lqt' (as is the case if you choose Qt in KDevelop's project
options), then the linker looks for a file libqt.so in standard
locations and perhaps in directories listed in the environment
variable LIBRARY_PATH. This file must be a symbolic link to the
actual library. So if you want to link with Qt 2, then libqt.so
(in /usr/lib or /usr/X11R6/lib IIRC) must be a symbolic link to 

That should be all. There may be some pitfalls with the configure
relying on one version or the other though.


More information about the KDevelop mailing list