Subject: [Boost-build] What to do with simple_run_action in cross-compile testing?
From: Kuhl, Brian (brian.kuhl_at_[hidden])
Date: 2016-04-22 23:42:46
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?
Manager - Information Development
kuhlenough @ skype
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk