configure looks for KDE libs/header in Qt2.x MDI app

[M.H.]

Hi,
it looks like I have another problem with Qt2.x MDI apps.
When I create a new project of this type or when I try to install from the
tarball, configure always checks for KDE libs/headers.
My questions:
-A Qt2.x MDI app is a "pure" Qt2.x app; is there a need to check for
the existence of KDE libs/headers ?
-Furthermore I haven't installed any KDE2 stuff; does it make sense 
to check for KDE1 libs/headers in a Qt2.x app?
-This check prevents the installation of my app on systems that don't have
KDE libs installed at all (afaik those systems still exist)? Or won't configure break
with an error message in this case? (Somehow I couldn't try this, because 
configure always finds my KDE libs/headers, even if I point KDEDIR to the wrong 
dir.)
-Or is this just a kind of bug?
Thanks a lot and sorry for the long mail !
Michael

BTW: (sorry if this is a little stupid)
Am I on the "right" Kdevelop version ?
I updated via cvsup with (found it somewhere in the archive)

*default host=cvsup.kde.org
*default base=/opt/sourcepackages
*default prefix=/opt/sourcepackages
*default release=cvs
*default compress
*default delete
*default tag=KDEVELOP_1_0
*default use-rel-suffix
kdevelop

Kdevelop tells me, that it is version 1.1 (no beta).
I first tried with *default tag=KDEVELOP, but what I received didn't compile
at all. Did I get a KDE2 version this way?