Bug#29380: using qt in terminal application

[Ralf Nolden]

On Friday, 20. July 2001 11:28, you wrote:
> Package: kdevelop
> Version: 2.0 (using KDE 2.2.0 beta1)
> Severity: normal
> Installed from:    compiled sources
> Compiler:          gcc version 2.95.2 20000220 (Debian GNU/Linux)
> OS:                Linux (i686) release 2.4.4
> OS/Compiler notes:
>
> If I generate a terminal application, the qt library does not appear to be
> accessible.
>
> Turning on the link with qt option doesn't seem to modify the configure
> script to check for qt and include the appropriate compiler options (e.g.,
> -Ipath/qt/include, etc.).
That is logical as you are not supposed to do that :) Seriously, the Qt/KDE 
templates are almost identical and you can turn a Qt-only program into a KDE 
program with the appropriate checks, but not a C++/C only terminal program as 
you're missing the complete stuff that automates moc, uic etc. This is why 
you need to generate a Qt-application to create one, otherwise we would 
pollute a C/C++ terminal application with  a few 100kb of unnecessary data 
for the checks and stuff, which is what you don't want if you just want to 
write a little commandline tool.

Ralf
-- 
--
We're not a company, we just produce better code at less costs.
--------------------------------------------------------------------
Ralf Nolden
nolden at kde.org

The K Desktop Environment	The KDevelop Project
http://www.kde.org		http://www.kdevelop.org


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«