Boost logo

Boost :

Subject: Re: [boost] PSA: Travis OS X bottleneck, <cxxstd> new Boost.Build feature
From: Tom Kent (lists_at_[hidden])
Date: 2017-10-27 17:04:35

It seems like this would be a great instance where the steering committee
could allocate some of the organization's funds to directly improve the
infrastructure being used by our team. I believe that we could upgrade our
Travis account to a paid one for a couple hundred a month to get more build

They also claim on that:

> Testing your open source project is 10000% free
> Seriously. Always. We like to think of it as our way of giving back to a
community that gives us so much as well.

Maybe we just need to have someone on the project contact them and get our
free quota raised?


On Thu, Oct 26, 2017 at 11:43 AM, Peter Dimov via Boost <
boost_at_[hidden]> wrote:

> Travis's OS X resources for open source projects seem to be insufficient,
> so OS X jobs are very slow and seem to be falling further and further
> behind. Therefore, library authors are encouraged to keep the OS X jobs to
> the minimum necessary. Spawning many OS X jobs takes hours (~25 minutes
> waiting time per job at a quick estimate).
> On a not entirely unrelated note, Rene Rivera has added a new feature
> <cxxstd> to Boost.Build that controls the C++ standard in use. So for
> instance, instead of the old
> b2 libs/mylib/test toolset=gcc cxxflags=-std=c++11
> one can now use
> b2 libs/mylib/test toolset=gcc cxxstd=11
> In addition to being more convenient, this also allows several invocations
> to be combined into one:
> b2 libs/mylib/test toolset=clang cxxstd=03,11,14,1z
> which can be leveraged to cut down on the number of jobs.
> An example of using cxxstd in .travis.yml can be seen here:
> _______________________________________________
> Unsubscribe & other changes:
> /listinfo.cgi/boost

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