Changes between Version 2 and Version 3 of Programming/Cpp/Boost/BuildingBoostOnMinGw


Ignore:
Timestamp:
Feb 18, 2016, 7:28:26 PM (6 years ago)
Author:
Vijay Varadan
Comment:

text alignment fixes

Legend:

Unmodified
Added
Removed
Modified
  • Programming/Cpp/Boost/BuildingBoostOnMinGw

    v2 v3  
    3232./bootstrap.sh --with-toolset=mingw
    3333}}}
    34 Note that the documentation on the boost wiki is wrong. You '''__must__''' pass the toolset you want to use using the above syntax for boost build to build in mingw. Simply passing gcc or mingw will cause the build to fail with something like this in the error log:
     34   Note that the documentation on the boost wiki is wrong. You '''__must__''' pass the toolset you want to use using the above syntax for boost build to build in mingw. Simply passing gcc or mingw will cause the build to fail with something like this in the error log:
    3535{{{#!bash
    3636$ sh bootstrap.sh
     
    7575}}}
    7676
    77 That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, `--build-type=complete`
     77   That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, `--build-type=complete`
    78788. Check the build log for errors, you should have 12 failures due to missing unicode/uversion.h which you can safely ignore ( some internal check for optional stuff that should be warnings ). At the end of the build process, you should have the boost libs installed in `~/build/output/boost_1_51_0/lib` and headers in the boost subdir under `~/build/output/boost_1_51_0/include/boost-1_51`.
    7979'''Note:''' Header files in mingw are in nested one level deeper than in posix builds i.e. in posix the dir structure looks like `$BOOST_ROOT/include/boost` and in mingw it's `$BOOST_ROOT/include/boost-1_51/boost`. So, when using boost in multi-platform builds like I do, you need to adjust your include path accordingly.