Re: [Boost-build] using "using" to make separate toolset configurations

Subject: Re: [Boost-build] using "using" to make separate toolset configurations
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2015-10-30 14:31:29

AMDG

On 10/30/2015 10:59 AM, Robert Ramey wrote:
> in my user-config.jam file I have:
> 
> using darwin : 03 : /hpc-5.1/usr/local/bin/g++ : <cxxflags>"-std=c++03" ;
> using darwin : 11 : /hpc-5.1/usr/local/bin/g++ : <cxxflags>"-std=c++11" ;
> using darwin : 14 : /hpc-5.1/usr/local/bin/g++ : <cxxflags>"-std=c++14" ;
> using clang : 03 : : <cxxflags>"-std=c++03"
> <cxxflags>"-Wno-c++11-extensions" ;
> using clang : 11 : : <cxxflags>"-std=c++11" ;
> using clang : 14 : : <cxxflags>"-std=c++14" ;
> 

  The version is expected to be the compiler's
actual version number.  It's possible that
the fact that you're treating it as an
arbitrary tag may be causing a problem
somewhere.  I believe that naming like
like 4.9~cpp11 is semi-standard for
making such distinctions.

> 
> my intention is to be able to use
> 
> ../../../tools/library_status/library_test.sh -j4 toolset=darwin-11
> variant=debug link=static >b2.log  &
> 
> ../../../tools/library_status/library_test.sh -j4 toolset=darwin-11
> variant=debug link=static >b2.log &
> 
> etc.
> 

I don't know anything about library_test.  Are
the arguments passed though to b2 with no
additions or modifications?

> But when run
> 
> ../../../tools/library_status/library_test.sh -j4 toolset=darwin-03
> variant=debug link=static test_array_xml_warchive  >b2.log  &
> 
> I get
> 
> boost_root: /Users/robertramey/WorkingProjects/modular-boost
> locate_root: /Users/robertramey/WorkingProjects/modular-boost
> uild core (at
> /Users/robertramey/WorkingProjects/modular-boost/tools/build/src) is
> 2015.07-git
> MPI auto-detection failed: unknown wrapper compiler mpic++
> Please report this error to the Boost mailing list: http://www.boost.org
> You will need to manually configure MPI support.
> Performing configuration checks
> 
>     - 32-bit                   : no  (cached)
>     - 64-bit                   : yes (cached)
>     - arm                      : no  (cached)
>     - mips1                    : no  (cached)
>     - power                    : no  (cached)
>     - sparc                    : no  (cached)
>     - x86                      : yes (cached)
>     - symlinks supported       : yes (cached)
>     - Boost.Config Feature Check: cxx11_hdr_array : no  (cached)
>     - Boost.Config Feature Check: cxx11_hdr_array : no  (cached)
> ...found 1 target...
> 
> on the other hand, when I invoke
> 
> ../../../tools/library_status/library_test.sh -j4 toolset=darwin-11
> variant=debug link=static test_array_xml_warchive >b2.log &
> 
> things work just fine.  What do I have to do to make this work.
> 

  I don't see any obvious reason why it shouldn't
work.  --debug-building should show what
Boost.Build is doing.

In Christ,
Steven Watanabe