Re: Cannot Compile KMailCool 1.6.2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Montag, 27. Januar 2003 02:25, Robert Tilley wrote:
> When I run ./configure --prefix=$KDEDIR && make install, a complaint about
> my version of Qt is spit back.
Don't use KDEDIR, don't use QTDIR.
KDE finds its stuff automatically with kde-config, Qt checks include the
debian path's where Qt is located. (/usr/lib and /usr/include/qt). If you
want to explicitely pass those, use ./configure --with-qt-libraries=/usr/lib
- --with-qt-includes=/usr/includes/qt
Ralf
>
> I have the following qt:
>
> oracle@tillarium:~/kmailcool$ dpkg -l | grep libqt3
> ii libqt3 3.1.1+cvs.2002 Qt GUI Library (runtime files)
> ii libqt3-dev 3.1.1+cvs.2002 Qt GUI development files
> ii libqt3-helper 3.1.1+cvs.2002 Some helper libraries for qt-tools
> ii libqt3-mt 3.1.1+cvs.2002 Qt GUI Library (Threaded runtime version)
> ii libqt3-mt-mysq 3.1.1+cvs.2002 Mysql database plugin for Qt3 (Threaded)
> ii libqt3-mt-odbc 3.1.1+cvs.2002 ODBC plugin for Qt3 (Threaded)
> ii libqt3-mysql 3.1.1+cvs.2002 Mysql database plugin for Qt3
> ii libqt3-odbc 3.1.1+cvs.2002 ODBC plugin for Qt3
>
> and the complaint is:
>
> checking for Qt... configure: error: Qt (>= Qt 3.1 (20021021)) (library
> qt-mt) not found. Please check your installation!
> For more details about this problem, look at the end of config.log.
> Make sure that you have compiled Qt with thread support!
>
> I have libqt3-mt to handle the thread support. Do I need to explicitly
> compile qt for my machine with the thread support enabled?
> --
> Comments are most appreciated,
>
> Bob
- --
We're not a company, we just produce better code at less costs.
- --------------------------------------------------------------------
Ralf Nolden
nolden@kde.org
The K Desktop Environment The KDevelop Project
http://www.kde.org http://www.kdevelop.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+NNmuu0nKi+w1Ky8RArAFAJ9WYCSk6Cbmgms4XUHRA6x3g9ZTdgCdFTDL
BgNN3bOxnpGD7sl0PgPne30=
=1Tyj
-----END PGP SIGNATURE-----
Reply to: