Hi Jesse,
----- Original Message -----
> From: "Jesse Williamson" <jwilliamson@xxxxxxxx>
> To: "Matt Benjamin" <mbenjamin@xxxxxxxxxx>
> Cc: "Adam C. Emerson" <aemerson@xxxxxxxxxx>, "Sage Weil" <sage@xxxxxxxxxxxx>, "Allen Samuels"
> <Allen.Samuels@xxxxxxxxxxx>, "Ken Dreyer" <kdreyer@xxxxxxxxxx>, "Haomai Wang" <haomai@xxxxxxxx>,
> ceph-devel@xxxxxxxxxxxxxxx
> Sent: Monday, May 2, 2016 9:01:44 PM
> Subject: Re: building boost statically
>
> On Mon, 2 May 2016, Matt Benjamin wrote:
>
> So, just a quick update here: I used bcp to extract boost containers. This
> works nicely, but you end up with 1628 files. It's doing what it's
> /supposed/ to do, since part of the purpose is to provide all the
> dependencies (for example, Boost::MPL is used), but that seems like maybe
> not what we want to do.
Yes. I experimented with this, but it didn't seem at all compact enough to be preferable to just building boost. The latter, building just what Ceph uses from boost now, took less than a minute on a single core (i7).
>
> Just using the boost/container headers is also possible, at a bit of risk
> that if we try to build on a system where one of the dependencies is
> incompatible in some way, Ceph won't build (perhaps a fairly low risk, but
> I'm throwing it out there). If that risk is acceptable, then we wouldn't
> have a large set of headers, but in effect would still be shipping our own
> little mini-fork.
I experimented with this also. What I found was that the number of boost internal (including unexposed) dependencies is much larger than container. This is a marvel of efficiency for the boost library internally, but isn't helpful for extracting a single like small_vector. In particular, conflicts with an installed boost are many.
>
> CMake looks like it has a module that can help us, and the general
> direction during an IRC chat was that we should do this as part of the
> move to cmake, rather than fidding with autoconf.
That seems like a good idea.
Matt
>
> -Jesse
>
> > Just wanted to ++ this.
> >
> > Matt
> >
> > ----- Original Message -----
> >> From: "Adam C. Emerson" <aemerson@xxxxxxxxxx>
> >> To: "Jesse Williamson" <jwilliamson@xxxxxxxx>
> >> Cc: "Sage Weil" <sage@xxxxxxxxxxxx>, "Allen Samuels"
> >> <Allen.Samuels@xxxxxxxxxxx>, "Ken Dreyer" <kdreyer@xxxxxxxxxx>,
> >> "Haomai Wang" <haomai@xxxxxxxx>, ceph-devel@xxxxxxxxxxxxxxx
> >> Sent: Monday, May 2, 2016 12:14:50 PM
> >> Subject: Re: building boost statically
> >>
> >> On 02/05/2016, Jesse Williamson wrote:
> >>> I think that in the long run, rather than bundling or using bcp, it would
> >>> be
> >>> nice to have cmake/autoconf let you point to the boost version you'd like
> >>> to
> >>> use.
> >>
> >> If we could manage it, that would be my ideal world. Rather than
> >> making it A Submodule, say, if we could have cmake examine the system
> >> boost to see what version it is and, if the version is greater than or
> >> equal to the required version, just use it. Otherwise just fetch the
> >> required version and build against it statically.
> >>
> >> --
> >> Senior Software Engineer Red Hat Storage, Ann Arbor, MI, US
> >> IRC: Aemerson@{RedHat, OFTC, Freenode}
> >> 0x80F7544B90EDBFB9 E707 86BA 0C1B 62CC 152C 7C12 80F7 544B 90ED BFB9
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> >> the body of a message to majordomo@xxxxxxxxxxxxxxx
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
> >
> > --
> > Matt Benjamin
> > Red Hat, Inc.
> > 315 West Huron Street, Suite 140A
> > Ann Arbor, Michigan 48103
> >
> > http://www.redhat.com/en/technologies/storage
> >
> > tel. 734-707-0660
> > fax. 734-769-8938
> > cel. 734-216-5309
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> >
>
--
Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://www.redhat.com/en/technologies/storage
tel. 734-707-0660
fax. 734-769-8938
cel. 734-216-5309
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
