Re: [jamboost] V2 testsuite improvements

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-02-25 07:52:47

David Abrahams wrote:

> >> python default_build.py --ignore-config
> >
> > Eh... the "--ignore-config" argument is not passed to bjam invocations.
> > Do you think it should?
>
> Not neccessarily. What's it supposed to do?

It supressed loading of site-config.jam/user-config.jam (as documented
in docs).

> >> 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.
>
> Do you agree?

Yes. And I believe there's a way:

alias.py borland

creates some borland targets

> >> 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?
>
> Nope. Did you try testing with Borland?

The above invocation fails. The reason is that 'prepare_suffix_map' is called
with "gcc" as parameter. And... I really don't understand what

prepare_suffix_map(pass_toolset and 'gcc' or self.toolset)

is supposed to do.

> >> 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.
>
> Apparently it isn't.

Hmm... I don't see why.

> > 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.
>
> By what mechanism is this test going to find another toolset then?

1. If you declare another toolset in site-config.jam, the test should be
able to use it.
2. If you create test-config.jam adn declare another toolset there,
the test should be able to use it. 

The "import gcc; " statement only adds another toolset. It does not disable 
those already configured in test-config.jam or site-config.jam

- Volodya