On Wed, Feb 15, 2017 at 10:50 AM, Stefan Seefeld <stefan@seefeld.name> wrote:
On 15.02.2017 11:39, Rene Rivera wrote:
>
> You can specify multiple features in the command like to indicate the
> collective requirement request of what you want to build. Hence if you
> configure the python interpreter with conditions that match that build
> request it should use that interpreter only. That's assuming it wasn't
> broken though :-(

OK. But all existing bugs in the implementation aside, I think this is
more of a UI concern: If I understand correctly, the "python" feature
expects values that express versions (so I can select a python config on
the command line with "<python>2.7".
my question is about what happens if the version alone isn't an
unambiguous discriminator, i.e. if I need to distinguish between a
64-bit python and a 32-bit python, both using the same version 2.7 ? How
can I express that, both on the command line as well as in my
user-config.jam configuration with the `using` rule ?

Given Tom's example user-config you can: 

b2 python=2.7 address-model=32
b2 python=2.7 address-model=64
b2 python=3.5 address-model=32
b2 python=3.5 address-model=64

To build them individually. And if you plan on installing you'd have to install to different locations as address-model doesn't tag the built products. You can also build multiple combinations in one go with:

b2 python=2.7,3.5 address-model=32
b2 python=2.7,3.5 address-model=64

Or all the combinations with:

b2 python=2.7,3.5 address-model=32,64

I believe the general build request option syntax is documented. But I leave finding that doc as an exercise for the reader ;-) 


--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail