I’ve been running  the test suite from the  ../status directory with:

../b2           ..         testing.lancher=./vxworks_boost_test_run.exp

The expect script telnets to the target system, changes to the mapped ../status directory, executes the test and harvests the return value to report as the exit value of the script.

This works great,  ( python and MPI  use testing.launcher but neither are supported by VxWorks so there’s no conflict).

What isn’t working is the pre-config tests that use  simple_run_action in ../libs/config/checks/Jamfile.v2

I’ve ignored then up to this point, but variadic macros are being erroneously disabled.

Do I just disable the whole thing for VxWorks because I trust the static configuration, or do I insert an alternate action that uses the testing.lancher ?

What’s the purpose pre-config tests, are they seen as integral part of the test suite?

Brian Kuhl

Manager – Information Development

Wind River

(250)807-7970 cell:(250)469-4644

kuhlenough @ skype