Re: [jamboost] Re: Re: [V2] includes not working

From: Jürgen Hunold (hunold+lists.Boost_at_[hidden])
Date: 2003-10-30 03:17:17

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Volodya !

On Thursday 30 October 2003 08:51, Vladimir Prus wrote:

> Thanks. I've now got the tar.gz that gmane has stripped.
>
> Now to your problem: I'm not sure there is one. Looking at your
> command line:
>
> g++ -x c++ -Wall -ftemplate-depth-100 -O0 -fno-inline -g
> -DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG
> -DBOOST_SIGNALS_NAMESPACE=boost_signals -DDATE_TIME_INLINE
> -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT
> -DQT_THREAD_SUPPORT -I"/ive/hunold/packages/boost" -I"/usr/include"
> -I"/usr/local/gcc-3.3.2 qt-3.2.2/include" -I"qtlib/include"

This is for 

gcc.compile.c++ ../../../build/qtlib/app/bin/gcc/debug/threading-multi/
main.o, right ?

> Isn't the last element what you're after? Maybe, "/usr/include" is
> the place where QT is installed? At least, that's what I get, besides
> -I"qtlib include".

Well, Qt installation is I"/usr/local/gcc-3.3.2/qt-3.2.2/include" , due 
to ABI incompatibilities for gcc-3.3.2.

I've taken a closer look and the problems seems to affect only lib 
targets. Please take a look at 

gcc.compile.c++ ../../../build/qtlib/lib/gui/bin/gcc/debug/
threading-multi/hello_world_widget.o

g++ -x c++ -Wall -ftemplate-depth-100 -O0 -fno-inline -g  
- -DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG 
- -DBOOST_SIGNALS_NAMESPACE=boost_signals -DDATE_TIME_INLINE 
- -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT 
- -DQT_THREAD_SUPPORT -I"/ive/hunold/packages/boost" -I"/usr/include" 
- -I"/usr/local/gcc-3.3.2/qt-3.2.2/include" -I"../../../build/qtlib/lib/
gui/bin/gcc/debug/threading-multi" -c -o "../../../build/qtlib/lib/
gui/bin/gcc/debug/threading-multi/hello_world_widget.o" "../../../
build/qtlib/lib/gui/bin/gcc/debug/threading-multi/
hello_world_widget.cpp"

I have
1. Boost Include . correct, because <use>boost is specified.
2. /usr/include I don't know where this comes from.
3. qt include correct, generated by qt.jam
4. implicit dependency because an uic-generated file is compiled. 
Correct.

But the correct <include>include path is missing.
This should be -I"../qtlib/include" for the lib target, too. 

I have the same effect in my real programs. Targets in exe Path are 
built correct, but compilation of library target fails due to missing 
include paths...

Yours,

Jürgem

- -- 
* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau
* voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover  
* fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover
* hunold_at_[hidden] ! www.ive.uni-hannover.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/oMkNljbJ/LLrxrYRAmj4AKCmBcQsk5DE+zRf9pIdyuFxutQpzACfUtA8
LJ09DrhEP/+XeD4YfSo2GNI=
=bzUp
-----END PGP SIGNATURE-----