Changes between Version 11 and Version 12 of TryModBoost
- Timestamp:
- Nov 19, 2013, 7:14:21 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TryModBoost
v11 v12 7 7 * A C++ compiler installed 8 8 9 == Choose a protocol for cloning == 10 11 The [https://github.com/boostorg/boost Boost super-project and libraries on GitHub] support cloning via HTTPS or SSH protocols. SSH is often used by developers, but HTTPS is preferable for those behind corporate firewalls. To use HTTPS instead of SSH, replace {{{git@github.com:boostorg/boost.git}}} in the examples below with {{{https://github.com/boostorg/boost.git}}}. 12 13 === Authentication === 14 15 The Boost super-project and libraries have been set up using relative URLs, so whichever protocol you use in the {{{git clone}}} command will determine how subsequent access to the super-project and libraries is authenticated. 16 9 17 == Installing Modular Boost == 10 18 11 From the command line on Window :19 From the command line on Windows: 12 20 13 21 {{{ 14 git clone --recursive https://github.com/boostorg/boost.git modular-boost22 git clone --recursive git@github.com:boostorg/boost.git modular-boost 15 23 cd modular-boost 16 24 .\bootstrap … … 21 29 22 30 {{{ 23 git clone --recursive https://github.com/boostorg/boost.git modular-boost31 git clone --recursive git@github.com:boostorg/boost.git modular-boost 24 32 cd modular-boost 25 33 ./bootstrap.sh … … 28 36 29 37 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. 30 31 From this point on, modularized Boost behaves a lot like pre-modularized Boost.32 38 33 39 == Experimenting == … … 55 61 56 62 should run the tests for Boost.system, all of which should pass. 63 64 == Developing == 65 66 === Checking out a particular branch === 67 68 The {{{clone}}} operation above leaves the {{{modular-boost}}} local repository, including the individual libraries, in a zombie-like state that is not very useful and can result in data loss. So the first thing you want to do is switch to the branch you want to work on: 69 70 {{{ 71 git checkout develop 72 }}} 73 74 {{{develop}}} corresponds to svn {{{trunk}}}, and is the starting point for simple changes that do not justify creating a new branch. 75