Re: [jamboost] QT support, and some problems

From: Jürgen Hunold (hunold+lists.Boost_at_[hidden])
Date: 2003-01-20 05:08:59

On Monday 20 January 2003 10:30, Vladimir Prus wrote:

> > You should add "-L$(QTDIR)/lib" to the gcc command line when qt
> > compilation is turned on. I haven't yet tried it out with Kylix
> > because it sure suffers from the same problem (BTW, bc++ also
> > understands the -L option).
>
> I've tried to fix that. Can you please check again?

Thanks ! I've tried and it links fine. Execution is another matter, for 
I use a customised Qt which is not in ld.so.conf nor in LD_LIBRARY_PATH 
due to conflicts with KDE-3.x.

The answer is to hadrcode the library with -Wl,-rpath, for gcc.
Another change is to link against qt-mt (Multi-Thread).
I wonder about detecting this somehow...

RCS file: /cvsroot/boost/boost/tools/build/new/qt.jam,v
retrieving revision 1.2
diff -u -r1.2 qt.jam
--- qt.jam	20 Jan 2003 09:25:53 -0000	1.2
+++ qt.jam	20 Jan 2003 10:02:10 -0000
@@ -41,7 +41,7 @@
 
rule qt.add-properties ( property )
{
- return <include>$(.prefix)/include <linkflags>-L$(.prefix)/lib 
<linkflags>-lqt ;
+ return <include>$(.prefix)/include 
<linkflags>-Wl,-rpath,$(.prefix)/lib <linkflags>-L$(.prefix)/lib 
<linkflags>-lqt-mt ;
}
 

> > I had a look at the Jamfile and it looks very good and seems to be
> > very easy to use. However, as several people, among them yourself,
> > pointed out in the thread "Adding QT support to Boost Build V2" it
> > really isn't a good idea to introduce that ".qpp" extension. As I
> > already explained to Jürgen, the moc can be seen as a tool in the
> > spirit of Doxygen that processes regular C++ files and extracts
> > information from them. So leaving the header file extension at ".h"
> > (or ".hpp", maybe) actually does make more sense from that point of
> > view. After all, we don't want to use a different extension for
> > each header file that is to be processed by a certain tool.
>
> OK, I'll change that.

Thanks ! 

I'll try and compile some other simple tools if you have finished the 
change.

BTW, how do I link against external libraries ? I would need STLport i 
order to test with something real ? I've tried to figure out something 
from boost.python Jamfile.v2, but did not succeed.

Yours, 

Jürgen

-- 
* 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