1.57.0 beta 1 is now available
Boost release 1.57.0 beta 1 is now available from SourceForge See http://sourceforge.net/projects/boost/files/boost-binaries/1.57.0.beta.1/ This release contains no new libraries. For details of what's in the release, see http://www.boost.org/users/history/version_1_57_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team P.S. There are a couple of known problems with this beta: * There are problems building with MSVC 8.0 * There are some problems with range/detail/any_iterator.hpp. These will be fixed before the release.
On Tuesday, October 21, 2014 06:14 AM, Marshall Clow wrote:
Boost release 1.57.0 beta 1 is now available from SourceForge
See http://sourceforge.net/projects/boost/files/boost-binaries/1.57.0.beta.1/
This release contains no new libraries.
For details of what's in the release, see http://www.boost.org/users/history/version_1_57_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.
Please download the beta, give it a try, and report any problems you encounter.
http://www.boost.org/users/history/version_1_57_0.html Primary test compilers include Clang-3.6 (for C++14 mode), which is currently trunk, it's not released (and probably won't be for some time). Ben
On 21 October 2014 04:08, Ben Pope
http://www.boost.org/users/history/version_1_57_0.html
Primary test compilers include Clang-3.6 (for C++14 mode), which is currently trunk, it's not released (and probably won't be for some time).
Thanks for pointing that out, it should be fixed now.
Boost release 1.57.0 beta 1 is now available from SourceForge
See http://sourceforge.net/projects/boost/files/boost-binaries/1.57.0.beta.1/
Is there a reason this was put in the 'boost-binaries' folder instead of
On Mon, Oct 20, 2014 at 5:14 PM, Marshall Clow
Marshall Clow
Boost release 1.57.0 beta 1 is now available from SourceForge [...] Please download the beta, give it a try, and report any problems you encounter.
I tested the beta with MSVC 12.4 RC and MSVC 14 CTP4 with the following additional changes: - Asio 1.10.5 from master branch - TypeTraits 5c0474d + 9ad41f9 from develop (for MSVC14) - Config d9026f1 + 5288f7 from develop (for MSVC14) - Range 1617a51 from develop (for the Range compile breaks) I built all libraries, compiled some projects and ran their unit tests. There were no issues.
On 10/21/2014 02:14 AM, Marshall Clow wrote:
Boost release 1.57.0 beta 1 is now available from SourceForge
See http://sourceforge.net/projects/boost/files/boost-binaries/1.57.0.beta.1/
This release contains no new libraries.
For details of what's in the release, see http://www.boost.org/users/history/version_1_57_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.
Please download the beta, give it a try, and report any problems you encounter.
Two questions: - Do we need https://github.com/boostorg/build/commit/252b5aa019dd1b502892e406dc1cd91d128... to be merged to master? It was meant to see some hangs on Solaris, IIUC. - I'm about to merge couple other Boost.Build changes to master, mostly in Python port. I'm assuming that's as safe as it could be, but let me know if you think otherwise. Thanks, Volodya -- Vladimir Prus CodeSourcery / Mentor Graphics http://www.mentor.com/embedded-software/
On Oct 24, 2014, at 7:07 AM, Vladimir Prus
On 10/21/2014 02:14 AM, Marshall Clow wrote:
Boost release 1.57.0 beta 1 is now available from SourceForge
See http://sourceforge.net/projects/boost/files/boost-binaries/1.57.0.beta.1/
This release contains no new libraries.
For details of what's in the release, see http://www.boost.org/users/history/version_1_57_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.
Please download the beta, give it a try, and report any problems you encounter.
Two questions:
- Do we need https://github.com/boostorg/build/commit/252b5aa019dd1b502892e406dc1cd91d128... to be merged to master? It was meant to see some hangs on Solaris, IIUC.
Do we have any way to test this?
- I'm about to merge couple other Boost.Build changes to master, mostly in Python port. I'm assuming that's as safe as it could be, but let me know if you think otherwise.
If you think they’re safe (and they’ve been in use on develop for a while), then that’s OK. — Marshall
On 10/24/2014 10:05 PM, Marshall Clow wrote:
On Oct 24, 2014, at 7:07 AM, Vladimir Prus
wrote: On 10/21/2014 02:14 AM, Marshall Clow wrote:
Boost release 1.57.0 beta 1 is now available from SourceForge
See http://sourceforge.net/projects/boost/files/boost-binaries/1.57.0.beta.1/
This release contains no new libraries.
For details of what's in the release, see http://www.boost.org/users/history/version_1_57_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.
Please download the beta, give it a try, and report any problems you encounter.
Two questions:
- Do we need https://github.com/boostorg/build/commit/252b5aa019dd1b502892e406dc1cd91d128... to be merged to master? It was meant to see some hangs on Solaris, IIUC.
Do we have any way to test this?
Not me, thats why I'm asking.
- I'm about to merge couple other Boost.Build changes to master, mostly in Python port. I'm assuming that's as safe as it could be, but let me know if you think otherwise.
If you think they’re safe (and they’ve been in use on develop for a while), then that’s OK.
I've merged Boost.Build develop, as of 2f6ee88755153d0a9a669ae9e3a798212c42e218, to master. These commits remain not merged: Aaron Boman (1): Preserve order of properties in PropertySet. Jurko (5): Fix a dependecy --> dependency comment typo. Fix error message typo - same named targets with different properties. Fix dependendency --> dependency comment typo. Fix comment typos. Return valid exit code from Windows batch scripts. Noel Belcourt (1): Block SIGCHLD during select. kjedruczyk (1): Fixed null ptr dereference in executable_path on solaris when getexecname fails. For those, I either cannot judge their safety, or don't find them important enough to warrant cherry-picking. I'll be traveling until 28th, with not much of free time, so feel free to cherry-pick any of these, if necessary. - Volodya
Dear Boost
First of all thanks for all your great work. It is simply amazing.
We dowloaded 1.57 Beta 1 to test it, and have some first feedback for you.
On Visual C++ 2013 (12.0.21005.1) we compile a project with this code:
#include
Le 29/10/14 13:56, Johan Doré a écrit :
On Visual C++ 2013 (12.0.21005.1) we compile a project with this code:
#include
int _tmain(int argc, _TCHAR* argv[]) { int Temp = 0;
BOOST_SCOPE_EXIT(Temp) { Temp = 0; } BOOST_SCOPE_EXIT_END; return 0; }
Unfortunately this gives us the warning:
warning C4003: not enough actual parameters for macro 'BOOST_PP_EXPAND_I'
I suggest you to create a Track ticket. Vicente
On 10/29/2014 8:56 AM, Johan Doré wrote:
Dear Boost
First of all thanks for all your great work. It is simply amazing.
We dowloaded 1.57 Beta 1 to test it, and have some first feedback for you.
On Visual C++ 2013 (12.0.21005.1) we compile a project with this code:
#include
int _tmain(int argc, _TCHAR* argv[]) { int Temp = 0;
BOOST_SCOPE_EXIT(Temp) { Temp = 0; } BOOST_SCOPE_EXIT_END; return 0; }
Unfortunately this gives us the warning:
warning C4003: not enough actual parameters for macro 'BOOST_PP_EXPAND_I'
It is an expected warning from Boost PP, which can be ignored. The VC++ preprocessor is not a C++ standard conforming preprocessor so it gives warnings when none are necessary. There is virtually nothing that can be done against such warnings except to attempt to turn them off completely within Boost PP code. I will look into doing this but often it is impossible to do since VC++ often does not honor where the preprocessor warning actually takes place when an effort is made to eliminate the warning at that place.
participants (9)
-
Ben Pope
-
Daniel James
-
Edward Diener
-
Johan Doré
-
Marcel Raad
-
Marshall Clow
-
Tom Kent
-
Vicente J. Botet Escriba
-
Vladimir Prus