Boost logo

Boost :

From: David Abrahams (dave_at_[hidden])
Date: 2003-11-01 14:57:45

Misha Bergal <mbergal_at_[hidden]> writes:

> We are in the process of enhancing boost regression runs coverage and
> reporting.
> We've added Boost.Python and Boost.Spirit to our nightly runs. The
> following are issues we've encountered so far:
> 1. Boost.Python required some minor changes to msvc-stlport toolset -
> solved locally (see

Hmm, seems like the right answer is to put <stlport-iostream>on into
the default build settings of the test which fails.

> 2. The python test fail if run as a part of status/jamfile - runs fine
> if ran from libs/python/test (see log below)


> 3. The requirement of unique test names across all libraries is really
> hurting (see

I believe this is a problem in the table generation script, not in the
build system, correct?

> The table is messed up because Boost.Python and Boost.Preprocessor
> test names conflict with MPL ones.
> We would appreciate if the interested parties took a look at these.

Dave Abrahams
Boost Consulting

Boost list run by bdawes at, gregod at, cpdaniel at, john at