Changes between Version 7 and Version 8 of TryModBoost
- Timestamp:
- Jul 19, 2013, 1:39:55 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TryModBoost
v7 v8 8 8 == Installing Modular Boost == 9 9 10 From the command line :10 From the command line on Window: 11 11 12 12 {{{ 13 13 git clone --recursive https://github.com/boostorg/boost.git modular-boost 14 cd modular-boost 15 bootstrap 16 .\b2 headers 14 17 }}} 15 18 16 || '''Warning: The build tools are not working as of the moment, so the remaining instructions on this page don't work yet.''' || 19 Or, from the command line on POSIX-like operating systems: 20 21 {{{ 22 git clone --recursive https://github.com/boostorg/boost.git modular-boost 23 cd modular-boost 24 ./bootstrap.sh 25 ./b2 headers 26 }}} 27 28 The {{{b2 headers}}} step creates the {{{boost}}} sub-directory hierarchy and populates it with links to the headers in the include sub-directories of the individual projects. 17 29 18 30 From this point on, modularized Boost behaves a lot like pre-modularized Boost. … … 20 32 == Experimenting == 21 33 22 If you want to build b2 and Boost source libraries, run the usual command line script. For Windows, that would be:34 If you want to build the separately compiled Boost libraries, run the usual {{{b2}}} command. For Windows, that would be: 23 35 24 36 {{{ 25 bootstrap26 37 .\b2 27 38 }}} … … 30 41 31 42 {{{ 32 ./bootstrap.sh33 43 ./b2 34 44 }}} 35 45 36 If b2 isn't already in your path, you probablywant to add it now.46 If {{{b2}}} isn't already in your path, you might want to add it now. 37 47 38 48 Testing is done just the way it has always been done. For example,