Subject: Re: [boost] [test]portability of data test cases and build issues
From: Vicente Botet (vicente.botet_at_[hidden])
Date: 2012-11-05 07:57:19
Gennadiy Rozenal wrote
> Vicente J. Botet Escriba
> <vicente.botet <at>
> wanadoo.fr> writes:
>> I use to do the following without any issue
>> [ run ../example/a_test.cpp ]
> I already do something like this (in my case [ glob test_datasets/*.cpp ],
> if target name is thew same as directory name it will fail to build on
>> > 2. How do I tell that I want to pass compilation to gcc in toolset
>> > gcc-4.7 only?
>> > I've tried
>> > and
>> > and either one does not work.
> -std=c++11 does work, but I want to pass
>> > different options for different versions of gcc.
>> Wow, I'm really surprised you have troubles with this. You need to
>> define your toolsets in the user_config.jam file. I have for example
>> using gcc : 4.7.1 : /usr/gcc-4.7.1/bin/g++-4.7 ;
>> using gcc : 4.7.1x : /usr/gcc-4.7.1/bin/g++-4.7 :
> -std="c++11" ;
>> Someone has been requesting the addition of a 'std' feature that gives
>> the standard, but I don't think this has been implemented or even
> Why do I need to introduce new toolsets? toolset gcc, gcc-4.7, gcc-4.6
> works fine. Moreover the main point is to make it work on regression
> tester box,
> not mine. I need to eliminate failures in regression table. I want to pass
> option (different one) to compilers which support it and ignore test on
> compilers which do not have it. I can probably get the same result by
> the code, but I'd rather have it marked unsupported in regression table
> of fake pass.
Have you tried filtering the targets with
-- View this message in context: http://boost.2283326.n4.nabble.com/test-portability-of-data-test-cases-and-build-issues-tp4638066p4638155.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk