Re: [boost] Too many library variants

Taking this to the devel list... Jeff Garland wrote:
On Mon, 14 Nov 2005 20:17:00 -0500, David Abrahams wrote
Rene Rivera <grafik.list@redshift-software.com> writes:
Merrill Cornish wrote:
When I built Boost 1.33.0 for MinGW, I just specified the toolset. As a result I got 28! variants on the set of Boost libraries.
From the various file names, I can figure out most of the variants:
d = debug mt = multi-threaded s = static but there are other variants which aren't as obvious.
It's all explained in <http://www.boost.org/more/getting_started.html#Results>.
Rene, I get the impression that 28 variants is a lot more than most people want, at least at first. Maybe we shouldn't build all of them by default, and just supply enough to "get started?"
I think at one point Doug suggested that a single variant is the most common case, and I agree.
OK, but which ever variant one picks, dynamic, static, etc., will mean that some subset of the libraries will not get built as not all libraries support building in any variant. What was the variant that Doug suggested? By the way it's only 16 variants that get built. The rest are the result of not having the version tag so those are just either copies or symlinks. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

Rene Rivera wrote:
By the way it's only 16 variants that get built. The rest are the result of not having the version tag so those are just either copies or symlinks.
That's still pretty intimidating, and requires a lot of memory / disk / time to build. I totally agree that a single configuration should be picked by default. I don't know the technical details well enough, but couldn't the default be set by individual library maintainers ? Or redefined, if the boost-wide default configuration is inappropriate for a given library ? Also, I believe the build parameters used to build only a subset of the configurations, and the one used to build the 'system' layout deserve a much more prominent exposure in the docs. Each time I want to rebuild boost, I have to google around to remind myself of the options I want... And we are not even talking about bb1 vs. bb2 yet... Regards, Stefan
participants (2)
-
Rene Rivera
-
Stefan Seefeld