| 1 | = Getting Started with Modular Boost Library Maintenance = |
| 2 | [[PageOutline]] |
| 3 | |
| 4 | This page describes the mechanics of maintaining a Boost library using Git and Modular Boost. |
| 5 | |
| 6 | The intended audience is developers involved in the maintenance of existing Boost libraries. |
| 7 | |
| 8 | == Prerequisites == |
| 9 | |
| 10 | * A recent version of the Git version control system. [wiki:Git/GitHome Read about Getting Started with Git.] If you are new to Git, install it and experiment a bit before coming back here. |
| 11 | |
| 12 | * A (free) [http://www.github.com GitHub] account. [wiki:StartGitHub Read about Getting Started with GitHub.] |
| 13 | |
| 14 | * Your favorite compiler and development environment installed and working smoothly. |
| 15 | |
| 16 | * Modular Boost installed as described in [wiki:TryModBoost Getting Started with Modular Boost]. Be sure to run the suggested libs/system/tests tests to be sure your installation and compiler are working together. |
| 17 | |
| 18 | * b2 is in your path. That allows most of the command line examples given here to work on both Windows and POSIX-like systems. |
| 19 | |
| 20 | == Verify Tests Working == |
| 21 | |
| 22 | Before making any changes to you library, which we will call "mylib", be sure the test suite is working in the modular Boost environment: |
| 23 | |
| 24 | {{{ |
| 25 | cd /modular-boost/libs/mylib |
| 26 | git checkout develop |
| 27 | cd test |
| 28 | b2 |
| 29 | }}} |
| 30 | |
| 31 | The results should be the same as trunk tests before the conversion. If they aren't, you probably want to resolved that before proceeding. |
| 32 | |
| 33 | == Fix a simple bug == |
| 34 | |
| 35 | These commands are the same for any Git project, modular or not, so hopefully you are already familiar with them: |
| 36 | |
| 37 | {{{ |
| 38 | cd /modular-boost/libs/mylib ''# if needed'' |
| 39 | git checkout develop ''# if needed'' |
| 40 | ''# make edits'' |
| 41 | ''# test'' |
| 42 | git commit -m 'my bug fix' |
| 43 | git push origin develop |
| 44 | }}} |
| 45 | |
| 46 | Simple bugs are usually fixed on the {{{develop}}} branch - there is no need to first create a bug-fix branch. |
| 47 | |