Boost logo

Boost :

Subject: Re: [boost] Boost 1.65.0 Beta 1 Release Candidate 1
From: berne_at_[hidden]
Date: 2017-07-09 15:02:41

It is header only but it does depend on a number of non-header-only

With 1.64.0, b2 --with-coroutine2 did work and triggered the building of
thread, chrono, system, and context (and obviously no coroutine2 library
since b2 is header only). If this change is intentional because
coroutine2 is header-only then that's fine, but when header-only libraries
depend on non-header only libraries it was certainly useful to me to be
able to trigger their dependancies to build with b2 using --with-<x>
instead of having to manually figure out those dependancies and maintain
that list with future boost releases.

I'm aware of the ability to disable the warning. The documentation isn't
even needed since the warning itself provides instructions on how to
disable it, but I'm targetting c++17 so everything in the documentation
seems to suggest that I should focus on using coroutine2.

- Josh

On Sun, 9 Jul 2017, Oliver Kowalke via Boost wrote:

> 2017-07-09 15:27 GMT+02:00 Joshua Berne via Boost <boost_at_[hidden]>:
>> Hi,
>> I've been playing aournd with boost coroutines2 and maybe I'm just
>> confused about where this project is, but with 1.65 coroutines2 doesn't
>> seem to be buildable out of the box any longer:
> boost.coroutine2 is a header-only lib - b2 --with-<library> would not work
>> I've tried looking through mailing list archives for anything about the
>> status of coroutine2 to no avail, and coroutine still spits out warnings to
>> use coroutine2 when used. I'm not sure where in the build system things
>> hook in to fix this.
> boost.coroutine is deprecated - but you can disable the warning (see
> documentation)
> boost.coroutine2 requires some C++11 features (you need to apply
> cxxflags="-std=c++11" or equivalent)
> _______________________________________________
> Unsubscribe & other changes:

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