On Mon, May 4, 2015 at 12:11 PM, Stefan Seefeld <stefan@seefeld.name> wrote:
On 04/05/15 12:55 PM, Rene Rivera wrote:
> I'm trying to decipher what your goals are. Since I can't see what use
> case you are trying to solve. Are you:
> 1. Trying to support building BPL against an external system provided
> regular Boost install?
> 2. Support building BPL with a full Boost tree checkout?
> 3. Users building their apps with BPL already built and installed?
> 4. Something else?

I'm trying to do 1), i.e. assume a development platform with Boost
libraries preinstalled, then check out and work on boost.python,
building it against the system libs only.

OK, got it. And the modular BB support I wrote will not immediately help you. As this is not the use case I had. But it is a use case I want to support eventually. If you haven't already, you should look at the BB built-in external Boost lib support <https://github.com/boostorg/build/blob/develop/src/contrib/boost.jam>. I haven't used it so I can't claim any suitability. But it does implement the tagging search for built libs part.

Anyway.. I can try and help in your efforts on getting BPL built this way.

So to answer your earlier questions.. The direction to take is something like that boost.jam support. I.e. to refactor the parts of boostcpp.jam that could be hoisted into BB/contrib and then they could be used without duplication. Of course it's harder to come up with a nice interface for such things :-)

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