On 27.10.2015 19:58, Stephen Kelly wrote:
Chris Green wrote:
Ah, I see. It appears I was unclear on the difference between target and
test. What I actually want is the *test* property SKIP_RETURN_CODE,
which there does not seem to be any way to access via a generator
expression. Looks like I'm
Chris Green wrote:
> Ah, I see. It appears I was unclear on the difference between target and
> test. What I actually want is the *test* property SKIP_RETURN_CODE,
> which there does not seem to be any way to access via a generator
> expression. Looks like I'm out of look, unless this is an
On 10/27/2015 02:33 PM, Chris Green wrote:
Ah, I see. It appears I was unclear on the difference between target
and test. What I actually want is the *test* property
SKIP_RETURN_CODE, which there does not seem to be any way to access
via a generator expression. Looks like I'm out of look,
Ah, I see. It appears I was unclear on the difference between target and
test. What I actually want is the *test* property SKIP_RETURN_CODE,
which there does not seem to be any way to access via a generator
expression. Looks like I'm out of look, unless this is an upcoming feature?
Thanks for
Hi,
I have a function cet_test(), which allows a user to specify the details
of a test which will be executed via a wrapper, cet_exec_test. It calls
the CMake add_test() macro to set this up. The user may subsequently set
the SKIP_RETURN_CODE property on this test, which must be communicated
Hi,
I should add that I am using CMake 3.3.2.
Sorry for the omission,
Chris.
On 10/26/15 2:29 PM, Chris Green wrote:
Hi,
I have a function cet_test(), which allows a user to specify the
details of a test which will be executed via a wrapper, cet_exec_test.
It calls the CMake add_test()
On 26.10.2015 20:29, Chris Green wrote:
Hi,
I have a function cet_test(), which allows a user to specify the
details of a test which will be executed via a wrapper, cet_exec_test.
It calls the CMake add_test() macro to set this up. The user may
subsequently set the SKIP_RETURN_CODE property
