On 02.04.2015 00:45, Alexander Duda wrote:
Am 01.04.2015 um 19:13 schrieb Sylvain Joyeux <[email protected]
<mailto:[email protected]>>:
It is more than past time for that, so:
- do you see a better way ? (I would personally really avoid putting
them in the orogen project for clarity and compilation times)
- if you agree with the scheme, how would you feel about moving the
'test' packages along with the corresponding package (i.e.
tests-orogen-transformer would go in rock.core), but disabled by
default ?
-1 see below
For me the best solution would be to add the tests to the orogen
package itself.
orogen-camera/tests/tests.orogen
orogen-camera/tests/tasks/Task.hpp
…
I guess this is not supported by orogen. A fallback for me would be to
add all orogen unit tests of core orogen packages into one common
repository to not get too many repositories.
+1 for putting the in the orogen project itself instead of creating
anoteher one...
...the tests can be disabled by default and need (simlar to the
metadata-support) to be activated explicitly.
Matthias
_______________________________________________
Rock-dev mailing list
[email protected]
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
