Testing new toolset

This page describes the steps necessary for testing of a new toolset.

Configure the toolset

First, make sure the compiler is in PATH. Then, locate the Boost.Build V2 configuration file, user-config.jam. If you never heard about it, it's located in Boost.Build V2 root (tools/build/v2 directory in C++ Boost tree). Add one line to that file:

   using new_toolset_name ;

Don't forget the space character before the semicolon.

Try the simplest example

Go to the $(boost_build_root)/example/hello directory, and run

bjam new_toolset_name

Try running bin/$(new_toolset_name)/debug/hello. If there any errors, report them and stop.

Try more contrived example

Go to the $(boost_build_root)/example/libraries directory, and run

bjam new_toolset_name

Try running app/bin/$(new_toolset_name)/debug/app. If there any errors, report them and stop.

Run full regression tests

If you have Python installed, go to the $(boost_build_root)/test directory, and run

python test_all.py new_toolset_name

Report the results.