On Mon, Jun 1, 2009 at 2:12 PM, Sean Chittenden wrote:
> Ideally I'd like to see cmake(1) be able to issue the following commands:
>>>
>>> // Create foo_test
>>> gcc -o foo.o -c foo.c -DTESTING
>>> gcc -o foo_test foo.o
>>>
>>> // Create bar_test
>>> gcc -o foo.o -c foo.c
>>> gcc -o bar.o -c bar.
Ideally I'd like to see cmake(1) be able to issue the following
commands:
// Create foo_test
gcc -o foo.o -c foo.c -DTESTING
gcc -o foo_test foo.o
// Create bar_test
gcc -o foo.o -c foo.c
gcc -o bar.o -c bar.c -DTESTING
gcc -o bar_test foo.o bar.o
That help clarify? set_target_property() st
On Sat, May 30, 2009 at 4:48 PM, Sean Chittenden wrote:
> Is set_property(TEST foo_bar_test SOURCE foo_bar.c APPEND PROPERTY
>> COMPILE_FLAGS "-DTESTING") an an inclusive AND of the test requirements (for
>> property to be set we must be building the TEST foo_bar_test *and* the
>> SOURCE foo_bar.c
Is set_property(TEST foo_bar_test SOURCE foo_bar.c APPEND PROPERTY
COMPILE_FLAGS "-DTESTING") an an inclusive AND of the test
requirements (for property to be set we must be building the TEST
foo_bar_test *and* the SOURCE foo_bar.c) or is it an OR (for
property to be set we must be building
On Sat, May 30, 2009 at 12:23 PM, Sean Chittenden wrote:
> Hello.
>
> I'm incorporating an external library in to our source tree and would like
> to run the external library's regression tests. The library is C, however,
> and the convention for doing this is:
>
> /* Lib contents above */
> #ifd
Hello.
I'm incorporating an external library in to our source tree and would
like to run the external library's regression tests. The library is
C, however, and the convention for doing this is:
/* Lib contents above */
#ifdef TESTING
int main(int argc, char* argv[]) {
/* Do tests
}
#end
