|
Boost-Build : |
Subject: Re: [Boost-build] Cross compiling regession suite for VxWorks
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2015-12-31 11:21:42
Hi Brian,
Getting b2 to work in the 'status' directory is the first step in any case.
The run.py script just automates some things, like uploading the results,
but the tests are run in the same way.
HTH,
On Thu, Dec 31, 2015, 03:14 Kuhl, Brian <brian.kuhl_at_[hidden]> wrote:
> Hi boost experts,
> I've been fiddling with boost and VxWorks in my part time for the last few
> months and have gotten to the point where I can successfully cross build
> with one particular configuration with just some minor changes to
> tools/build/src/gcc.jam and builtin.jam and a custom project-config.jam.
> VxWorks 7 64bit Intel / GNU 4.8.1.5 / Dinkum C++11 /Linux build host
> /boost 1.59
>
> While I wait for our engineering group to address various bugs that will
> let me verify a more general solution, I'm trying to determine the best
> path to running the full regression reporting suite as described here:
> http://www.boost.org/development/running_regression_tests.html
>
> I've started by trying "To run every library's regression tests, run b2
> from <boost-root>/status directory."
>
> but that seems to be trying to build some tests that my environment
> doesn't support.
>
> So before I start debugging, I'd like to know how much this method
> overlaps with the:
> python run.py
> script, if I get the b2 build in /status to run, will the python script
> also work, or is python a reimplementation of the same thing?
>
> Happy holidays,
>
> Brian Kuhl
> Manager, Technical Content Engineering
> Wind River
>
>
> source ./vxworks_env.sh && \
> ./b2 install -j4 --prefix=/opt/vx7/workspace/VsbSim/usr/root
> --libdir=/opt/vx7/workspace/VsbSim/usr/lib/common
> --includedir=/opt/vx7/workspace/VsbSim/usr/h/public \
> link=static runtime-link=static toolset=gcc-vxworks
> target-os=vxworks \
> --with-atomic --with-chrono --with-context --with-coroutine
> --with-date_time --with-exception --with-filesystem --with-graph
> --with-iostreams --with-log --with-math --with-program_options
> --with-random --with-regex --with-serialization --with-system --with-thread
> --with-timer --with-test
> Performing configuration checks
> - 32-bit : no (cached)
> - 64-bit : yes (cached)
> - arm : no (cached)
> - mips1 : no (cached)
> - power : no (cached)
> - sparc : no (cached)
> - x86 : yes (cached)
> - symlinks supported : yes (cached)
> - lockfree boost::atomic_flag : no (cached)
> - has_icu builds : no (cached)
> - zlib : yes (cached)
> - compiler-supports-visibility : yes (cached)
> - compiler-supports-ssse3 : yes (cached)
> - compiler-supports-avx2 : yes (cached)
> - gcc visibility : yes (cached)
> - long double support : yes (cached)
> Component configuration:
> - atomic : building
> - chrono : building
> - container : not building
> - context : building
> - coroutine : building
> - coroutine2 : not building
> - date_time : building
> - exception : building
> - filesystem : building
> - graph : building
> - graph_parallel : not building
> - iostreams : building
> - locale : not building
> - log : building
> - math : building
> - mpi : not building
> - program_options : building
> - python : not building
> - random : building
> - regex : building
> - serialization : building
> - signals : not building
> - system : building
> - test : building
> - thread : building
> - timer : building
> - wave : not building
> ...patience...
> ...patience...
> ...patience...
> ...patience...
> ...patience...
> ...found 30903 targets...
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>
> --
Vladimir Prus
http://vladimirprus.com
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