Re: [libposix-development] [PATCH] strncpy implementation and tests

[Henrique A. <hd...@gm...>]

2009/7/16 Chris Forbes <ch...@fa...>:
> My point was to avoid having to do `add_posix_test()` in a cmake config file someplace; Instead I automatically determine the tests that exist,

 In that case I don't think that's necessary. Isolating the build
system from code has more advantages than disadvantages. For example,
it's easier to replace the build system and people that need to copy
the test code to their own projects don't need to worry about the
extra markup code. I'm planning splitting the main make file and
moving test rules to the tests directory (this task is available at
TaskFreak), so that the test list can grow without messing the root
CMakeLists.txt. The goal is to have a very simple 1 or 2 line command
sequence for specifying tests, for example:

 add_libposix_test(test_name source1 source2 source3 [INPUT
input_file] [EXPECTED_OUPUT output_file] [EXPECTED_ERROR error_file]
[INVERT_RESULT])

> and specify their dependencies at the same point where the test is defined (in the C file).
>


-- 
 Henrique Dante de Almeida
 hd...@gm...