Subject: Re: [boost] RFC: Separating Boost.Python from Boost
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2015-05-30 09:25:31
On 30 May 2015 at 11:43, Bjorn Reese wrote:
> I do not know why anyone want to do that for Boost.Python, but this
> problem is of a general nature.
> Every author of a new Boost library has to go through the "birth-pain"
> of getting their library to build with Boost.Build while it is not part
> of monolithic Boost yet.
> Currently, the easiest way is to checkout the Boost codebase and then
> copy your library in there. A more involved alternative is to cheat
> Boost.Build into believing that your library is part of the Boost code
> base by adding lots of symbolic links all around. Neither solution is
> feasible if you want other projects to use your library.
I'm a bit surprised you say this. AFIO requires exactly one symlink
into libs/. Modular Boost takes care of all the rest if your Boost
library has the right directory structure.
On Windows, enabling normal users to create symlinks also gets rid of
any weird build failure problems. Or you simply copy afio into
libs/afio and be done with it.
-- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk