| | 1 | = Testing new toolset = |
| | 2 | |
| | 3 | This page describes the steps necessary for testing of a new toolset. |
| | 4 | |
| | 5 | == Configure the toolset == |
| | 6 | |
| | 7 | First, make sure the compiler is in {{{PATH}}}. Then, locate the Boost.Build V2 configuration file, {{{user-config.jam}}}. If you never heard |
| | 8 | about it, it's located in Boost.Build V2 root (tools/build/v2 directory in C++ Boost tree). |
| | 9 | Add one line to that file: |
| | 10 | {{{ |
| | 11 | using new_toolset_name ; |
| | 12 | }}} |
| | 13 | Don't forget the space character before the semicolon. |
| | 14 | |
| | 15 | == Try the simplest example == |
| | 16 | |
| | 17 | Go to the {{{$(boost_build_root)/example/hello}}} directory, and run |
| | 18 | {{{ |
| | 19 | bjam new_toolset_name |
| | 20 | }}} |
| | 21 | If there any errors, report them and stop. |
| | 22 | |
| | 23 | == Try more contrived example == |
| | 24 | |
| | 25 | Go to the {{{$(boost_build_root)/example/libraries}}} directory, and run |
| | 26 | {{{ |
| | 27 | bjam new_toolset_name |
| | 28 | }}} |
| | 29 | If there any errors, report them and stop. |
| | 30 | |
| | 31 | == Run full regression tests == |
| | 32 | |
| | 33 | If you have Python installed, go to the {{{$(boost_build_root)/test}}} directory, and run |
| | 34 | {{{ |
| | 35 | python test_all.py new_toolset_name |
| | 36 | }}} |
| | 37 | Report the results. |
| | 38 | |
| | 39 | |