From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-02-25 01:58:10
David Abrahams wrote:
> >> Perfectly!
> > Good. Will commit relevant change in a minute.
> It's not quite working out for me.
> test-config.jam has to go in my BOOST_BUILD_PATH, but not in my home
Yes. The use case I meant is dropping test-config.jam into tools/build/test
> Even when I specify --ignore-config on the test command-line
> python default_build.py --ignore-config
Eh... the "--ignore-config" argument is not passed to bjam invocations. Do you
think it should?
> It still tries to use msvc to do the build. There should be a way to
> specify the toolset to test from the command-line. It seems like
> BoostBuild.py is supposed to be taking care of that, but it doesn't
> look like it's working.
Did you overcome the problem already?
> Also, default_build.py is supposed to force gcc, isn't it? Then why
> is it using $toolset?
No, it's supposed to be generic. The "import gcc ; " line in project-root.jam
file that the test generates was placed there before test-config.jam could
be used to declare toolsets for testing.
> I'm a little confused, I guess...
Hope something is more clear now.
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