Re: [Boost-build] really dumb bjam question(2)

Subject: Re: [Boost-build] really dumb bjam question(2)
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2012-07-15 00:27:04

AMDG

On 07/14/2012 10:09 PM, Robert Ramey wrote:
> Steven Watanabe wrote:
>> I don't understand.  --dump-tests is intended to
>> be used by the automated regression test system.
>> All is does it to print a list of test cases.
>> I've never used it for my own tests.
>>
>> The log should indicate which tests failed
>> and the output from them.  What more do you need?
>> If bjam just says:
>> "...found 7263 targets..."
>> it means that all the targets are up to date
>> which implies that all the tests passed.
> 
> Ahh - I use  in the library_test.sh script to
> produce an html table with the cumulative results.
> Basically to run regression tests on one library
> on my machine. That's what I need the --dump-tests for.
> 
> What I would really like to have is to be able
> to define some target like "test_results" so I wouldn't
> need the scripts .  But this would probably be a lot
> more complicated than the current script so I
> won't ask for this..
> 

It would be nice.  In some ways it would
be simpler than the current script, since
it wouldn't need to parse the output.

>> I expect it to work too, and it does for me.
>> Can you reduce this to a small self-contained
>> project that I can look at?
> 
> whoops - my mistake - the above case does work.  The
> case I would like to see work is
> 
> import os ;
> 
> BOOST_INCLUDE_PATH = [ os.environ BOOST_ROOT ]  ;
> ECHO $(BOOST_INCLUDE_PATH)
> 

Missing ';'

> project safe_numerics
>     # : source-location ... # not needed for header files
>     : requirements
>         #<include>"C:/BoostRelease"
>         <include>$(BOOST_INCLUDE_PATH)
>         <toolset>gcc:<cxxflags>-pedantic
>         <toolset>gcc:<cxxflags>-std=c++0x
>     # : default-build   - default none
>     # : build-dir - default = ./bin
> ;
> 
> I've also tried
> 
>         <include>[ os.environ BOOST_ROOT ]
> 

That can't work because of the way tokenization
and variable expansion are defined.

> which didn't work either.  My intention is to permit the
> current value of environmental BOOST_ROOT to be passed
> as the include directory.
> 

It ought to work.  A literal and
a variable that contains a single
string should behave exactly the same.

In Christ,
Steven Watanabe