Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2003-02-23 12:04:46

Vladimir Prus <ghost_at_[hidden]> writes:

>> > The little remaining thing is: declare all toolsets eligible for testing
>> > in one place. I just got this idea:
>> >
>> > 1. First, the system looks for a file called test-config.jam, and if
>> > found, it will set up toolsets.
>> > 2. Otherwise, site-config.jam and user-config.jam are loaded and should
>> > do the same.
>> >
>> > Is this sensible?
>> 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

Even when I specify --ignore-config on the test command-line

python --ignore-config

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 is supposed to be taking care of that, but it doesn't
look like it's working.

Also, is supposed to force gcc, isn't it? Then why
is it using $toolset?

I'm a little confused, I guess...

Dave Abrahams
Boost Consulting

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at