Changes between Initial Version and Version 1 of BoostRegressionsV2

Timestamp:

Feb 16, 2006, 2:55:43 PM (20 years ago)

Author:

ghost

Comment:

--

BoostRegressionsV2

@@ +1 @@
+
+= Running C++ Boost regressions with Boost.Build V2 =
+
+This document described how to run C++ Boost regression tests (using regression.py script), with Boost.Build V2.
+
+== Configuration ==
+
+Unlike V1, configuration of toolset is not done by creating new toolset files. Rather, there's a single config file that
+should be edited. The file is called {{{user-config.jam}}} and must be placed to your home directory. For the exact meaning of "home directory", see http://boost.org/boost-build2/doc/html/bbv2/reference.html#bbv2.reference.init
+
+The file should contain one entry for each toolset/version combination to be tested. Each entry should be in the form:
+{{{
+using <toolset-name> : <toolset-version> : <absolute name of compiler executable> ;
+}}}
+for example:
+{{{
+using msvc : 7.0 : "Z:/Programs/Microsoft Visual Studio/vc98/bin/cl.exe" ;
+}}}
+
+It's possible to specify additional options to compiler or linker:
+{{{
+using hp_cxx 
+       : 65_042_tru64   # version
+       :                # command not specified -- use default
+       :                # options
+     <cflags>"-version V6.5-042"
+     <ldflags>"-version V6.5-042 -use_non_shared_libcxx"
+;
+}}}
+
+Another note is that while in V1 customized toolset is common named {{{base-toolset}}}-{{{version}}}, in V2 the version parameter to {{{using}}} should not include base toolset name. That is, using {{{hp_cxx_64_042_tru64}}} above would be a mistake.
+
+After declaring a toolset version, it's possible to use {{{base-toolset}}}-{{{version}}} to request this toolset when building.
+
+= Running =
+
+To use V2 when running {{{regression.py}}}, just add {{{-v2}}} option. For example:
+
+{{{
+./regression.py setup --v2
+./regression.py test --v2 --toolsets=hp_cxx-65_042_tru42
+./regression.py collect-logs --v2
+}}}
+
+The names of toolsets passed to {{{regression.py}}} are constructed from name base toolset name and version passed to the {{{using}}} rule, separated with dash.
+
+
+
+
+