Boost logo

Boost :

Subject: Re: [boost] [1.58.0] Release candidates available
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2015-04-07 04:00:57

On Tue, Apr 7, 2015 at 10:45 AM, Olaf van der Spek <ml_at_[hidden]> wrote:
> On Mon, Apr 6, 2015 at 6:38 PM, Stephan T. Lavavej
> <stl_at_[hidden]> wrote:
>> [Rene Rivera]
>>> If you search back through email history you'd find that it used to be the
>>> default. But was changed as doing complete was: rarely what end users
>>> wanted, used up gobs of disk space, and made the build take a really long
>>> time (there might be other reasons but I don't remember ATM).
>> On my 3-year-old dev box with a spinny hard drive, extracting Boost 1.57.0 takes 4 minutes, and a complete x86 build plus cleanup takes 10 minutes, resulting in 2.03 GB of headers and DLLs/LIBs. Neither seems especially onerous, aside from the fact that the Getting Started documentation doesn't say to use a parallel build, which is *really* bad.
> Could b2 default to -jX where X is the number of cores?

This would be unexpected and detrimental if there is not enough RAM.

Boost list run by bdawes at, gregod at, cpdaniel at, john at