22 May
2014
22 May
'14
8:54 a.m.
Hello Lars
I believe that Boost.Build is designed to ignore as much as possible of the environment it happens to be in, so that you can provide particular versioned toolsets to it > and it'll Do The Right Thing.
But does it respect the environment settings if run in a shell set up for VS2012 when 2013 is also present? Further to that , we also have straight-forwardly wrong behaviour exhibited by B2 when you pass it a non-existent tool-chain name. Like msvc in my example. It still builds ...
patches.
Fair enough. I am game. How do I do this? VBR. Jerry