i need build boost regression test suite on build machine (linux) , run on sut (target machine, linux). necessary boost libraries installed on sut shared ones. have installed gcc toolchain on build machine. sut has no gcc @ all.
i have built bjam on build machine native utility. have cross-compiled useful utility (process_jam_log , library_status) described here: http://www.boost.org/doc/regression/library_status/doc/library_status.html
the main idea build (cross-compile) overall regression test suite on build machine, copy sut , run on latter. when bjam builds test tries run test on build machine in native environment.
decisions boost.org have found (e.g. http://www.boost.org/development/running_regression_tests.html) suppose wants build , run test suite on machine boost libraries installed on. seems case doesn't mentioned in google.
my question how force bjam miss run stage? or how reach intention elsewhere?
upd. have got pretty convenient script framework. framework can build test suite on build machine, deploy on sut (target), run on target, overall useful information launch , analyse whether test suite passes or fails. that's why i'm searching decision operates overall test suite not separate tests.
for cross-compiled testing need use helper script/program running of compiled test executables. need to:
- write script takes single argument being path test executable. script need to:
- copy executable target os machine.
- remote execute the test program on target os machine.
- capture output , result code @ target os machine.
- print output , return result code @ host os machine.
- indicate test running script "testing.launcher=" when running testing builds.
the testing.launcher build property documented in boost build testing documentation.
Comments
Post a Comment