Subject: Re: [Boost-build] Building Boost with multiple python versions
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2017-02-15 00:51:33
On 14.02.2017 19:20, Edward Diener via Boost-build wrote:
> For compilers one can always do:
> using some_compiler : n.n ; some_path : some_requirements ;
> using some_compiler : n.nsome_string ; some_path : some_requirements ;
> as in:
> using gcc : 6.3 :
> using gcc : 6.3c03 :
> : <cxxflags>-std=c++03 ;
> and if I run 'b2 toolset=gcc-6.3 etc.' it will use the first of the
> using statements and if I run 'b2 toolset=gcc-6.3c03 etc.' it will use
> the second of the two using statements.
Interesting, but also quite counter-intuitive: A line such as
using gcc : 6.3 ;
suggests the build system is instantiating a gcc toolchain with version
6.3. (Assume a platform with multiple compiler versions, it would have
to validate that it really picks a matching version !)
using gcc : 6.3c03 ;
that pattern is broken, as there is no compiler that would report
"6.3c03" as version string.
So the obvious question is : what is the second argument to the "using"
rule above ? Is it a version or is it not a version ?
> Ideally one should be able to do something similar with python.
> I have no idea how these things work internally, but just mention what
> I have noticed works for me.
Understood. So the question above goes to the boost.build developers. :-)
-- ...ich hab' noch einen Koffer in Berlin...
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk