Precompiled Boost

Boost Libraries

[http://www.boost.org]

I compile different versions of the Boost Libraries with MSVC. I have written a batch script to ease this process. To use it you basically need the source code (tarball or SVN), Cygwin and Microsoft Visual Studio. I primarily compile these libraries to add support for localization through Boost.Locale and Boost.Regex, as well as Python (via Boost.Python).

The binaries posted here are experimental and any comments would be welcome.

If you are looking for older builds, go to the Precompiled Boost (Past Builds) page.

Boost v1.61

Updated: 22 September 2016
Notes for library users:
- All statically built libraries link against the static runtimes (/MT instead of /MD).
- Boost.Locale and Boost.Regex are now statically linked against ICU libraries. This is currently unsupported upstream. [see tickets in Boost.Locale: 9685 and Boost.Regex: 12011]
- When using static Boost.Python libs, you may need to define BOOST_PYTHON_STATIC_LIB through your preprocessor.
- These libraries are exclusively built for Windows; no, they are not intended to work on Linux.
Notes for rebuilding the libraries:
- Links:
  - Source Code: http://sourceforge.net/projects/boost/files/boost/1.61.0/
  - Batch Script: build-boost_1.61.0.bat
  - User Configuration: [user-config.jam] and [user-config64.jam]
  - Patch(es): [boost_1.61.0.patch]
- Instructions:
  - You need Cygwin to use my build script.
  - Download the batch script (build-boost_1.61.0.bat) and all user configuration files user-config.jam, user-config64.jam (and place all of them in the same directory).
  - Download and decompress the official sources in their own directory.
  - Follow the instructions at the bottom of this page on how to setup Python for 32- and 64-bit systems. (or look here)
  - You will need a working installation of Python. You can obtain Python from https://www.python.org/downloads/windows/
  - Download the Precompiled ICU libraries and decompress them in an appropriate directory.
  - Check and modify the configuration options in the build-boost_X.XX.X.bat script.
  - Build everything: build-boost_X.XX.X.bat build all
  - Package everything: build-boost_X.XX.X.bat package all

Precompiled Boost
Compiler	Download	Size	Arch	Build	Link	Notes
MSVC 2015	boost-1.61.0-x86-vs2015.7z [md5]	66.9 MB	x86 (32-bit)	debug release	shared static	Compiled using MSVC Update 3, ICU v57.1 and Python v2.7.10
MSVC 2015	boost-1.61.0-x64-vs2015.7z [md5]	76.3 MB	x64 (64-bit)	debug release	shared static	Compiled using MSVC Update 3, ICU v57.1 and Python v2.7.10
MSVC 2013	boost-1.61.0-x86-vs2013.7z [md5]	67.4 MB	x86 (32-bit)	debug release	shared static	Compiled using ICU v57.1 and Python v2.7.10
MSVC 2013	boost-1.61.0-x64-vs2013.7z [md5]	81.1 MB	x64 (64-bit)	debug release	shared static	Compiled using ICU v57.1 and Python v2.7.10
MSVC 2012	boost-1.61.0-x86-vs2012.7z [md5]	73.9 MB	x86 (32-bit)	debug release	shared static	Compiled using ICU v57.1 and Python v2.7.10
MSVC 2012	boost-1.61.0-x64-vs2012.7z [md5]	89.5 MB	x64 (64-bit)	debug release	shared static	Compiled using ICU v57.1 and Python v2.7.10
MSVC 2010	boost-1.61.0-x86-vs2010.7z [md5]	60.7 MB	x86 (32-bit)	debug release	shared static	Compiled using ICU v57.1 and Python v2.7.10
MSVC 2010	boost-1.61.0-x64-vs2010.7z [md5]	79.9 MB	x64 (64-bit)	debug release	shared static	Compiled using ICU v57.1 and Python v2.7.10
MSVC 2008	boost-1.61.0-x86-vs2008.7z [md5]	60.5 MB	x86 (32-bit)	debug release	shared static	Compiled using ICU v57.1 and Python v2.7.10
MSVC 2008	boost-1.61.0-x64-vs2008.7z [md5]	78.6 MB	x64 (64-bit)	debug release	shared static	Compiled using ICU v57.1 and Python v2.7.10

Python v2.7.5 (for Boost.Python)

Download the latest 2.x python release of Python. I have not tested using Python 3.x to build Boost.Python, but it may work as well. For this post I used v2.7.5 which can be found at:

You can extract the two files into convenient directories from the command line:

msiexec /a python-2.7.5.msi /qb TARGETDIR=I:\dev\python
msiexec /a python-2.7.5.amd64.msi /qb TARGETDIR=I:\dev\python64

Disclaimer

Downloads in this website are exclusively here for my own personal use and have not been properly tested or verified.

#1 | Written by Java Development about 7 years ago. Reply

Thank you for this great article, I have shared it on Facebook.

0
#2 | Written by rupert about 7 years ago. Reply

Hi, I used your boost files in VS2015 but you are missing libboost_regex-vc140-mt-gd-1_61.lib and so it failed. As you have libboost_regex-vc140-mt-sgd-1_61.lib I tried removing the sgd and leaving just gd in the filename but this did not work.

0
#3 | Written by phil about 8 years ago. Reply

Hello all, is there already a patch for the current boost 1.64.0? thx

0
- #4 | Written by stathis about 8 years ago. Reply
  
  I haven’t made one. Should I? I am not sure if anyone is using those … or ? :)
  
  0
  - #5 | Written by Dukeling about 8 years ago. Reply
    
    I definitely am, and would appreciate updates :)
    
    0
#6 | Written by Rob about 8 years ago. Reply

Very strange build…. Have a look at the libboost_thread files, compared to the libboost_system
This can not be used when compiling under debug mode

0
- #7 | Written by stathis about 8 years ago. Reply
  
  The builds can be used just fine in debug mode, at least to the best of my knowledge. You should provide an example or be a bit more specific on what the problem is, otherwise I cannot address it. Please also understand exactly what these builds are useful for (which in my case is to be able to compile fully static binaries — static build + static runtime). Alternatively, you could perfectly do one of the following: (a) use the official Boost builds, or (b) download my scripts, modify and build your own (which is so people don’t have to complain when it doesn’t work for them).
  
  cheers.
  
  0
#8 | Written by omardavinci about 8 years ago. Reply

i only get the archive is corrupt like in this:
boost-1.61.0-x86-vs2012.7z

Can someone upload boost without corrupt archives?? plss

0
- #9 | Written by stathis about 8 years ago. Reply
  
  There are no corrupt archives, especially the one you are mentioning is not. Use the md5 checksum file to verify. In case you are struggling using my builds, please download the official Boost (http://www.boost.org/), use their docs and official mailing lists and forums for help.
  
  0
#10 | Written by Mark about 8 years ago. Reply

“All statically built libraries link against the static runtimes (/MT instead of /MD).”
Why? Previously you included mt-gd versions of all *.lib, and now only few.
Hence:
http://i.imgur.com/oYSQRRB.png

Isn’t a /MDd options default for debugging?

0
- #11 | Written by stathis about 8 years ago. Reply
  
  I have not changed the way I build Boost. I checked some of the older archives and I don’t see libboost_filesystem-mt-gd-1_XX.lib, I assume that I never built it in the past, or have I? in which archive was that? I tend to never mix static/dynamic runtimes, but I appreciate there are cases where this may be necessary. Is it mandatory for you to build against a dynamic runtime, yet link in static boost? (because the one you find in the archives has a static runtime….which eh, maybe will cause you trouble down the line?)
  
  0
- #12 | Written by stathis about 8 years ago. Reply
  
  /MDd is good when you are debugging a dynamically linked binary, if you are doing a static link use /MTd.
  
  0
#13 | Written by Mark about 8 years ago. Reply

Hello!

Did you build it with VS2015 Update >=2?
Please see this:
https://connect.microsoft.com/VisualStudio/feedback/details/1892487

0
- #14 | Written by stathis about 8 years ago. Reply
  
  I believe it is VS2015 Update 2 I compiled with (given the time I compiled). Are you having that issue?
  
  0
  - #15 | Written by Mark about 8 years ago. Reply
    
    –Are you having that issue?
    Not (yet?:) ) Just going to use lockless stuff from boost and got that static assert notification from VS.
    
    Thanks for reply and your work!
    
    0
    - #16 | Written by stathis about 8 years ago. Reply
      
      Ok, I’m not familiar with that assertion, but as far as the builds are concerned: remember that you can always rebuild Boost with the scripts I provide in case you want to ensure a specific compiler was used or make any modifications. Good point that in the next iteration I will try to include versions of the tools used in a log, so there is no guesswork involved.
      
      0
      - #17 | Written by Mark about 8 years ago.
        
        — I’m not familiar with that assertion
        
        So this most likely means that you built it with Update <2. Because programmer have to add some macro definition manually to bypass that assertion. And boost seems to refuse to do that in library addressing it to user/programmer.
        http://boost.2283326.n4.nabble.com/lockfree-ENABLE-ATOMIC-ALIGNMENT-FIX-for-VS-2015-Update-2-td4685955.html
        
        0
      - #18 | Written by stathis about 8 years ago.
        
        Ok. So if you define _ENABLE_ATOMIC_ALIGNMENT_FIX and build with Update 2 (or later) it doesn’t go away?
        
        I interpret the information here https://blogs.msdn.microsoft.com/vcblog/2016/04/14/stl-fixes-in-vs-2015-update-2/ that it should work, but everything you use must be compiled with Update 2+.
        
        If it doesn’t work still, there is yet one other solution: I build boost with MSVC2015 Update 3. How about that?
        
        0
      - #19 | Written by Mark about 8 years ago.
        
        –but everything you use must be compiled with Update 2+.
        
        Seems like that, for binary compatibility.
        
        — I build boost with MSVC2015 Update 3
        That’s always reasonable, because of fixes and optimizations they provide with those updates. It would be nice if it doesn’t bother you too much.
        
        0
      - #20 | Written by stathis about 8 years ago.
        
        Ok try download the MSVC2015 of 1.61.0 I recompiled with Update 3. Let me know what happens.
        
        0
#21 | Written by Neo about 8 years ago. Reply

Thank you

0
#22 | Written by Darren about 9 years ago. Reply

Thank you so much. You’ve saved me a huge amount of work and effort. Building Boost.Python on Windows is extremely frustrating for a *nix guy. Thanks for making this available.

0
#23 | Written by Bob Kocisko about 9 years ago. Reply

Thank you!! Using your batch file I was able to build Boost v1.58 with ICU 55.1 using Visual Studio 2013. That was a huge relief after spending 14 hours trying to build them myself, debugging my Cygwin installation, batch and bash files and having an all-around terrible time :).

I am a little confused though about one config option used in your batch file: SSBUILDER_ROOT. What is this used/needed for?

0
- #24 | Written by stathis about 9 years ago. Reply
  
  SSBUILDER_ROOT is an environment variable pointing to my own build system where i keep and develop various things. In the boost build script if you search, it is effectively adding the !SSBUILDER_ROOT!\bin dir to the PATH. That dir contains 7zip, patch, etc. you normally can ignore it. I will plan for removing it on next release.
  
  0

sigmoid

Precompiled Boost

Boost Libraries

Boost v1.61

Python v2.7.5 (for Boost.Python)

Disclaimer

Leave a Comment