Re: [Boost-build] modular builds

Subject: Re: [Boost-build] modular builds
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2015-05-07 00:05:29

On 04/05/15 11:22 PM, Rene Rivera wrote:
> On Mon, May 4, 2015 at 12:11 PM, Stefan Seefeld <stefan_at_[hidden]
> <mailto:stefan_at_[hidden]>> 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 :-)

Hi Rene,

thanks for offering your help ! The above boost.jam file looks indeed
very useful (at least the documentation in the file heading sounds
exactly like what I need). However, I'm still not entirely sure how I
would use this. Let's assume I drop this into my boost.python tree, at
least initially. How would I use it from my Jamfile ?
Also, given that my original error was about the boostcpp.jam file (and
its definition of the "tag" rule), would I substitute a call to
boostcpp.tag by one of the tagging rules from boost.jam ? (And, what
*is* tagging, actually ? A way to define a library name ?)

Many thanks,
        Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...