aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/_posts
diff options
context:
space:
mode:
authorEgor Tensin <Egor.Tensin@gmail.com>2017-01-07 23:50:59 +0300
committerEgor Tensin <Egor.Tensin@gmail.com>2017-01-07 23:50:59 +0300
commit3dbb71f6b99433bae23ea8ae9e0dfd5661e043de (patch)
treed29edd88ba4fa8aba7c792f6a89dcf8ecd43bef6 /_posts
parentmake the sidebar two-column (diff)
downloadjekyll-theme-3dbb71f6b99433bae23ea8ae9e0dfd5661e043de.tar.gz
jekyll-theme-3dbb71f6b99433bae23ea8ae9e0dfd5661e043de.zip
add "Building Boost on Windows"
Diffstat (limited to '_posts')
-rw-r--r--_posts/2017-01-07-building-boost.md220
1 files changed, 220 insertions, 0 deletions
diff --git a/_posts/2017-01-07-building-boost.md b/_posts/2017-01-07-building-boost.md
new file mode 100644
index 0000000..193b786
--- /dev/null
+++ b/_posts/2017-01-07-building-boost.md
@@ -0,0 +1,220 @@
+---
+title: Building Boost on Windows
+layout: post
+excerpt: >
+ This post describes the process of building Boost on Windows using either
+ Visual Studio or the combination of Cygwin & MinGW-w64.
+---
+Below you can find the steps required to build Boost libraries on Windows.
+These steps tightly fit my typical workflow, which is to use Boost libraries in
+CMake builds using either Visual Studio or the combination of Cygwin &
+MinGW-w64.
+I would expect, however, that the procedure for the latter toolset can easily
+be adjusted for generic GCC distributions (including vanilla GCCs found in
+popular Linux distributions).
+
+One of the features of this workflow is that I build throwaway, "run once on
+each VM, record the results, and scrap it" executables not more often than not,
+so I prefer to link everything statically, including for instance the C/C++
+runtimes.
+This is implemented by passing `runtime-link=static` to Boost's build utility
+`b2`; change this to `runtime-link=dynamic` to link the runtime dynamically.
+
+Visual Studio
+-------------
+
+Statically-linked Boost libraries are built by default, both the debug and the
+release versions of them.
+While it is required to keep x86/x64 libraries in different directories (to
+avoid file name clashes), it's not necessary to separate debug libraries from
+their release counterparts, because that information is actually encoded in
+file names (the "gd" suffix).
+
+### x86
+
+```
+> cd
+D:\workspace\third-party\boost_1_61_0\msvc
+
+> bootstrap
+...
+
+> b2 --stagedir=stage\x86 ^
+ runtime-link=static ^
+ --with-filesystem ^
+ --with-program_options ^
+ ...
+...
+```
+
+### x64
+
+The only important difference is that you have to pass `address-model=64` to
+`b2` (notice also the different "stage" directory).
+
+```
+> cd
+D:\workspace\third-party\boost_1_61_0\msvc
+
+> bootstrap
+...
+
+> b2 --stagedir=stage\x64 ^
+ runtime-link=static ^
+ address-model=64 ^
+ --with-filesystem ^
+ --with-program_options ^
+ ...
+...
+```
+
+Cygwin + MinGW-w64
+------------------
+
+Contrary to the Visual Studio example above, it is required to store debug and
+release libraries *as well as* x86 and x64 libraries in different directories.
+It is required to avoid file name clashes; unlike the Visual Studio "toolset"
+(in Boost's terms), GCC-derived toolsets don't encode any information (like
+whether the debug or the release version of a library was built) in file names.
+
+Also, linking the runtime statically doesn't really make sense for MinGW, as it
+always links to msvcrt.dll, which is [simply Visual Studio 6.0 runtime].
+
+[simply Visual Studio 6.0 runtime]: https://sourceforge.net/p/mingw-w64/wiki2/The%20case%20against%20msvcrt.dll/
+
+In the examples below, only the debug versions of the libraries are built.
+Build the release versions by executing the same command, and substituting
+`variant=release` and the proper "stage" directory path.
+
+### x86
+
+```
+> cd
+/cygdrive/d/workspace/third-party/boost_1_61_0/mingw
+
+> ./bootstrap.sh
+...
+
+> cat user-config-x86.jam
+using gcc : : i686-w64-mingw32-g++ ;
+
+> ./b2 toolset=gcc-mingw \
+ target-os=windows \
+ link=static \
+ variant=debug \
+ --stagedir=stage/x86/debug \
+ --user-config=user-config-x86.jam \
+ --with-filesystem \
+ --with-program_options \
+ ...
+...
+```
+
+### x64
+
+Notice the two major differences from the x86 example:
+
+* `b2 address-model=64 ...` (as in the example for Visual Studio),
+* the different user configuration file, pointing to `x86_64-w64-mingw32-g++`
+instead of `i686-w64-mingw32-g++`.
+
+Again, as in the example for Visual Studio, a different "stage" directory needs
+to be specified using the `--stagedir` parameter.
+
+```
+> cd
+/cygdrive/d/workspace/third-party/boost_1_61_0/mingw
+
+> ./bootstrap.sh
+...
+
+> cat user-config-x64.jam
+using gcc : : x86_64-w64-mingw32-g++ ;
+
+> ./b2 toolset=gcc-mingw \
+ address-model=64 \
+ target-os=windows \
+ link=static \
+ variant=debug \
+ --stagedir=stage/x64/debug \
+ --user-config=user-config-x64.jam \
+ --with-filesystem \
+ --with-program_options \
+ ...
+...
+```
+
+Usage in CMake
+--------------
+
+### Visual Studio
+
+Examples below apply to Visual Studio 2015.
+You may want to adjust the paths.
+
+#### x86
+
+```
+> cd
+D:\workspace\build\test_project\msvc\x64
+
+> cmake -G "Visual Studio 14 2015" ^
+ -D BOOST_ROOT=D:\workspace\third-party\boost_1_61_0\msvc ^
+ -D BOOST_LIBRARYDIR=D:\workspace\third-party\boost_1_61_0\msvc\stage\x86\lib ^
+ -D Boost_USE_STATIC_LIBS=ON ^
+ -D Boost_USE_STATIC_RUNTIME=ON ^
+ ...
+```
+
+#### x64
+
+```
+> cd
+D:\workspace\build\test_project\msvc\x86
+
+> cmake -G "Visual Studio 14 2015 Win64" ^
+ -D BOOST_ROOT=D:\workspace\third-party\boost_1_61_0\msvc ^
+ -D BOOST_LIBRARYDIR=D:\workspace\third-party\boost_1_61_0\msvc\stage\x64\lib ^
+ -D Boost_USE_STATIC_LIBS=ON ^
+ -D Boost_USE_STATIC_RUNTIME=ON ^
+ ...
+```
+
+### Cygwin & MinGW-w64
+
+Examples below only apply to debug CMake builds.
+Notice that, contrary to the Visual Studio examples above, debug *and* release
+builds must be kept in separate directories.
+You may also want to adjust the paths.
+
+#### x86
+
+```
+> cd
+/cygdrive/d/workspace/build/test_project/mingw/x86/debug
+
+> cmake -G "Unix Makefiles" \
+ -D CMAKE_BUILD_TYPE=Debug \
+ -D CMAKE_C_COMPILER=i686-w64-mingw32-gcc \
+ -D CMAKE_CXX_COMPILER=i686-w64-mingw32-g++ \
+ -D BOOST_ROOT=/cygdrive/d/workspace/third-party/boost_1_61_0/mingw \
+ -D BOOST_LIBRARYDIR=/cygdrive/d/workspace/third-party/boost_1_61_0/mingw/x86/debug/lib \
+ -D Boost_USE_STATIC_LIBS=ON \
+ ...
+```
+
+#### x64
+
+```
+> cd
+/cygdrive/d/workspace/build/test_project/mingw/x64/debug
+
+> cmake -G "Unix Makefiles" \
+ -D CMAKE_BUILD_TYPE=Debug \
+ -D CMAKE_C_COMPILER=x86_64-w64-mingw32-gcc \
+ -D CMAKE_CXX_COMPILER=x86_64-w64-mingw32-g++ \
+ -D BOOST_ROOT=/cygdrive/d/workspace/third-party/boost_1_61_0/mingw \
+ -D BOOST_LIBRARYDIR=/cygdrive/d/workspace/third-party/boost_1_61_0/mingw/x64/debug/lib \
+ -D Boost_USE_STATIC_LIBS=ON \
+ ...
+```