From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-06-19 04:12:57
[moving this to mailing list, as it's of general interest]
On Friday 16 June 2006 02:08, Bronek Kozicki wrote:
> Hello Volodya
> I'm trying to migrate tests to other machine (my laptop with external
> drive) where bjam v2 seems to work fine. Among tests that I'd like to run
> on new machine is mingw with stlport . The problem is that I do not know
> name of the toolset to use :( Toolsets that I use now (just started test,
> will see if its done by tomorrow morning) are: msvc-6.5, msvc-7.0,
> gcc-3.4.5_mingw, gcc-3.4.2_mingw . My user-config.jam is attached. BTW: is
> it msvc-6.5 or msvc-6.0 - which name is preferred? Obivously I have latest
> SP installed, that is SP6. Or maybe you would like me to run other tests?
I think mingw with stlport would be an interesting combination to test. I
believe Rene did some work recently to improve mingw, and also reported some
issues with STLport.
Can you start by going to say, tools/build/v2/example/libraries and running
bjam --v2 gcc-3.4.5_mingw stdlib=stlport
? If that goes well, let me know and I'll modify regression.py so that you can
or something. At the moment, embedded space in between toolset name and
stlport will confuse things.
Rene, does your recent report mean that STLport variants should be tested in
<threading>multi mode? I'm not quite sure what V1 does -- will it link to
STLport even if you request single threading, or what?
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk