Announce: Boost 1.50 installer for 32-bit Windows now available
With apologies to the community for not finding the time to release Windows installers for 1.48 and 1.49, we now have an installer for 1.50 available for immediate download: http://www.boostpro.com/download The version installs 32-bit libraries and/or DLLs for the following compilers: Visual C++ 8.0 (Visual Studio 2005) Visual C++ 9.0 (Visual Studio 2008) Visual C++ 10.0 (Visual Studio 2010) We are dropping support for Visual C++ 7.1 as of this time, unless someone wishes to contract us to bring it back. Also, although I have prepared a 64-bit installer, I have not yet found a solution for integrating it with the existing installer. If anyone with NSIS scripting experience would be willing to assist me, we'd be happy to provide a free installer which installs both 32-bit and 64-bit Boost libraries for applicable Windows platforms. Enjoy! -- John Wiegley BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
[John Wiegley]
The version installs 32-bit libraries and/or DLLs for the following compilers: Visual C++ 8.0 (Visual Studio 2005) Visual C++ 9.0 (Visual Studio 2008) Visual C++ 10.0 (Visual Studio 2010)
I assume that they were built with VC8 SP1, VC9 SP1, and VC10 SP1? Mixing RTM and SP1 could be harmful. For example, if Boost's static libs were built with VC10 RTM, and linked into user code built with VC10 SP1, Boost's static libs could contain instantiations of basic_string that could be chosen by the linker (i.e. ODR violation!). If so, the user's executables would be affected by the basic_string memory leak, even though the user had upgraded to SP1 which fixed that (super bad) leak. STL
Stephan T Lavavej <stl@exchange.microsoft.com> writes:
I assume that they were built with VC8 SP1, VC9 SP1, and VC10 SP1? Mixing RTM and SP1 could be harmful. For example, if Boost's static libs were built with VC10 RTM, and linked into user code built with VC10 SP1, Boost's static libs could contain instantiations of basic_string that could be chosen by the linker (i.e. ODR violation!). If so, the user's executables would be affected by the basic_string memory leak, even though the user had upgraded to SP1 which fixed that (super bad) leak.
Yes, they are all built with SP1 versions of the related compilers. The build platform was Windows Server 2003 R2, with the Microsoft Cluster Compute Pack installed, and all other updates applied. -- John Wiegley BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
[John Wiegley]
Yes, they are all built with SP1 versions of the related compilers. The build platform was Windows Server 2003 R2, with the Microsoft Cluster Compute Pack installed, and all other updates applied.
Awesome! (The build platform shouldn't affect the output. I've seen a lot of crazy stuff, but not that - yet.) STL
John Wiegley <johnw@boostpro.com> writes:
We are dropping support for Visual C++ 7.1 as of this time, unless someone wishes to contract us to bring it back.
I was able to recreate the 7.1 build very easily, so that installation target is now available as well. Still no 64-bit solution as of yet. -- John Wiegley BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
participants (2)
-
John Wiegley -
Stephan T. Lavavej