Release 1.56.0 of the Boost C++ Libraries is now available.
These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications.
The Boost license encourages both commercial and non-commercial use.
This release contains one new library and numerous enhancements and bug fixes for existing libraries.
=== Modularization ===
Boost version control has migrated to a system using git submodules. This shouldn't make too much of a difference to users, although the directory structure is now a bit different.
Parts of some libraries have been moved into different modules, and several new modules have been extracted from existing code. All header paths should remain the same. The new modules are:
• Assert: Customizable assert macros. Maintained by Peter Dimov.
• Core: Core utilities used by other libraries, with minimal dependencies. Maintained by Peter Dimov, Glen Fernandes and Andrey Semashev.
• Lexical_Cast: General literal text conversions, such as an int represented a string, or vice-versa, from Kevlin Henney.
• Throw_Exception: A common infrastructure for throwing exceptions from Boost libraries, from Emil Dotchevski.
• Winapi: Windows API declarations without
On Thu, Aug 7, 2014 at 12:54 PM, Marshall Clow
Release 1.56.0 of the Boost C++ Libraries is now available.
The corresponding windows binaries for msvc-8.0 (SP1), msvc-9.0 (SP1), msvc-10.0 (SP1), msvc-11.0 (Update 4) and msvc-12.0 (Update 2) in 32 & 64 bit versions are now also available from sourceforge. http://sourceforge.net/projects/boost/files/boost-binaries/1.56.0/ Tom Kent
Is it possible to create a tag for each library saying boost_1_56 ? I'm sure I can figure out how to do this on my library - but can it be done globally before release is "opened" for updates? RObert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-1-56-0-has-been-released-tp4666140p... Sent from the Boost - Dev mailing list archive at Nabble.com.
On 8 August 2014 20:57, Robert Ramey
Is it possible to create a tag for each library saying boost_1_56 ?
I'm sure I can figure out how to do this on my library - but can it be done globally before release is "opened" for updates?
We were discussing doing this off list, but didn't really come to a conclusion. Although it can be done any time, as all the necessary information is in the super project, so it's okay to push to master before it's done - we don't tag the current master hash, we tag the hash from the super project's boost-1.56.0 tag. Since we stopped automatically updating the super project for a couple of weeks before the release some modules might have updated their master branch without it being included in the final release.
On 8/8/14, 1:54 AM, Marshall Clow wrote:
Release 1.56.0 of the Boost C++ Libraries is now available.
Congratulations to all! And thank you, Boost release team. You've done an incredible job! Regards, -- Joel de Guzman http://www.ciere.com http://boost-spirit.com http://www.cycfi.com/
On August 9, 2014 6:20:32 PM EDT, Joel de Guzman
On 8/8/14, 1:54 AM, Marshall Clow wrote:
Release 1.56.0 of the Boost C++ Libraries is now available.
Congratulations to all! And thank you, Boost release team. You've done an incredible job!
Indeed. With the git conversion, creating new modules, factoring out dependencies, and more, you fills have accomplished a great deal. Thank you for your hard work. ___ Rob (Sent from my portable computation engine)
participants (8)
-
Daniel James -
Ion Gaztañaga -
Joel de Guzman -
Klaim - Joël Lamotte -
Marshall Clow -
Rob Stewart -
Robert Ramey -
Tom Kent