Re: [jamboost] Toolset inheritance, Kylix

From: Felix E. Klee (felix.klee.jamboost_at_[hidden])
Date: 2003-01-28 16:38:37

On Thursday 23 January 2003 04:35 pm, Vladimir Prus wrote:
> >>>Yes, it works now. However, I had to change qt-mt into qt in new/qt.jam
> >>>since I didn't try to compile the multi threaded QT library for Kylix
> >>>yet. Shouldn't qt be the default and only be changed to qt-mt when
> >>><threading> is set to multi?
> >>
> >>You've right! Care to try fixing that? The add-properties rule in qt.jam
> >> is the key: just compute the library name depending on whether
> >> <theading>multi is in properties.
> >
> > OK, I'll try it, but probably not today; tomorrow evening is more likely.
>
> OK. Good luck.

Hm, I had a look at it last weekend but couldn't figure out how to make it 
work. I just don't know enough about the boost internals but I guess it is 
trivial for you to solve that problem.

Something else: Today I did a fresh install from the CVS and tried running 
bjam in examples-v2/qt but I got the following error messages:

/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
feature.jam:777: in feature.run-actions
*** argument error
* rule qt.qt.add-properties ( property )
* called with: ( <uses>qt : <os>LINUX <toolset>gcc <stdlib>native 
<link>shared <link-runtime>shared <optimization>off <threading>single 
<rtti>on <debug-symbols>on <hardcode-dll-paths>false <variant>debug <uses>qt
)
* extra argument <os>LINUX
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
qt.jam:72:see definition of rule 'qt.qt.add-properties' being called
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
targets.jam:536: in generate
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
targets.jam:482: in object(typed-target)@1.generate
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
targets.jam:286: in object(main-target)@1.generate
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
targets.jam:183: in object(project-target)@1.generate
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
build-system.jam:129: in load
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
modules.jam:171: in import
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/../new/
bootstrap.jam:41: in boost-build
/home/felix/projects/jo/src/boost-cvs/boost/tools/build/examples-v2/
boost-build.jam:2: in module scope

Am I doing something stupidly wrong or do you experience the same problems? 
BTW, the "hello", "libraries", and "make" examples work and, as you might 
guess, "qt-ui" doesn't. Some more info: I tried the examples with gcc (not 
Kylix) and the QT path is set correctly:

> ls $QTDIR/lib
libeditor.so@ libqt-mt.so@ libqt.so@ libqui.so@
libeditor.so.1@ libqt-mt.so.3@ libqt.so.3@ libqui.so.1@
libeditor.so.1.0@ libqt-mt.so.3.0@ libqt.so.3.0@ libqui.so.1.0@
libeditor.so.1.0.0* libqt-mt.so.3.0.5* libqt.so.3.0.5* libqui.so.1.0.0*

Felix

-- 
To contact me personally don't reply but send email to 
felix DOT klee AT inka DOT de