Re: [boost] To modularize, or not to modularize. What is the plan?

Subject: Re: [boost] To modularize, or not to modularize. What is the plan?
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2019-05-08 14:09:47

On Wed, May 8, 2019 at 7:24 AM James E. King III via Boost <
boost_at_[hidden]> wrote:

> On Tue, May 7, 2019 at 10:06 PM Peter Dimov via Boost
> <boost_at_[hidden]> wrote:
> >
> > Rene Rivera wrote:
> > > On Tue, May 7, 2019 at 8:41 PM Peter Dimov via Boost
> > > <boost_at_[hidden]> wrote:
> > > > Rene Rivera wrote:
> > > >
> > > > > * Ban relative use of inter-library dependencies.
> > > >
> > > > What does this mean?
> > >
> > > It means no doing "../../lib/thread/.." from some other lib to get at
> the
> > > build files or anything else.
> >
> > How will the libraries refer to each other? <library>/boost//libname,
> > target_link_libraries(Boost::libname), and rely on someone to have made
> > these available somehow? (If we're dropping the superproject.)
> >
> >
>
> Wouldn't we be able to make much simpler builds for each repository if
> we assume a third party package manager will handle acquiring our
> dependencies and tell us how to leverage them?

Yes.

>   If you want to stick
> with b2 we could add a b2 generator to conan so it would spit out some
> b2 rules,

That already exists <
https://docs.conan.io/en/latest/reference/generators/b2.html>.

> otherwise we could further simplify things by using cmake
> builds in each repository instead of b2.
>

Sure.. Actually you wouldn't care what build system a particular library
author used. As you could use whatever build system you prefer to both
produce and consume the libraries.

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net