[context] Trying to compile Coroutine on trunk

Hi, I don't reach to compile Boost.Coroutine under Mac using trunk ../../../boost/coroutine/coroutine.hpp:14:45: error: boost/context/stack_allocator.hpp: No such file or directory ../../../boost/coroutine/coroutine.hpp:15:41: error: boost/context/stack_utils.hpp: No such file or directory Are you changing the interface of Boost.Context? Best, Vicente

please use boost-1.51.0 - the version of boost.context in boost-trunk was modified. Therefore boost.coroutine will not compile with boost-trunk. regards, Oliver
Hi,
I don't reach to compile Boost.Coroutine under Mac using trunk
../../../boost/coroutine/coroutine.hpp:14:45: error: boost/context/stack_allocator.hpp: No such file or directory ../../../boost/coroutine/coroutine.hpp:15:41: error: boost/context/stack_utils.hpp: No such file or directory
Are you changing the interface of Boost.Context?
Best, Vicente
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

On Mon, Sep 10, 2012 at 08:32:43AM +0200, Oliver Kowalke wrote:
please use boost-1.51.0 - the version of boost.context in boost-trunk was modified. Therefore boost.coroutine will not compile with boost-trunk.
regards, Oliver
Hi,
I don't reach to compile Boost.Coroutine under Mac using trunk
../../../boost/coroutine/coroutine.hpp:14:45: error: boost/context/stack_allocator.hpp: No such file or directory ../../../boost/coroutine/coroutine.hpp:15:41: error: boost/context/stack_utils.hpp: No such file or directory
Are you changing the interface of Boost.Context?
Do we have any policies about leaving trunk broken. In the case of Context, no-one uses it yet, but for anything that someone depends on, breaking trunk for it breaks people that for some reason uses trunk. (also, we bottom-post inline on the Boost lists :D) -- Lars Viklund | zao@acc.umu.se

Do we have any policies about leaving trunk broken.
In the case of Context, no-one uses it yet, but for anything that someone depends on, breaking trunk for it breaks people that for some reason uses trunk.
what about evolution of the code/interface? boost-docu states: "Library Maintainer's Rights and Responsibilities: You are free to change your library in any way you wish, and you are encouraged to actively make improvements." The modification I've done was a request from one of the reviewers of boost.context. Oliver

Oliver Kowalke wrote
Do we have any policies about leaving trunk broken.
In the case of Context, no-one uses it yet, but for anything that someone depends on, breaking trunk for it breaks people that for some reason uses trunk.
what about evolution of the code/interface?
boost-docu states: "Library Maintainer's Rights and Responsibilities: You are free to change your library in any way you wish, and you are encouraged to actively make improvements."
The modification I've done was a request from one of the reviewers of boost.context.
You can always try be backward compatible. E.g. preserve the existing files, which could include the new ones. Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/context-Trying-to-compile-Coroutine-on-tr... Sent from the Boost - Dev mailing list archive at Nabble.com.
participants (4)
-
Lars Viklund
-
Oliver Kowalke
-
Vicente Botet
-
Vicente J. Botet Escriba