[Rock-dev] Removal of test deployments in oroGen projects

Matthias Goldhoorn matthias.goldhoorn at dfki.de
Tue Nov 20 11:32:48 CET 2012


On 20.11.2012 11:30, Sylvain Joyeux wrote:
> Since one can now use "default deployments" (i.e. you don't have to
> define a deployment but can use the 'my::Task' =>  '
> 'task_name' syntax in Orocos.run or rock-run my::Task), I would like to
> remove most deployments currently defined in the oroGen projects (some
> of them are still important as roby/syskit does not support default
> deployments yet).
>
> What triggers this is that (1) it would be welcome cleanup and (2) the
> ROS integration is using catkin scripts which forcefully define a 'test'
> target. Since it is pretty common that the deployments are called
> 'test', it breaks the build.
>
> Thoughts ?
>
+1,

but why we cant consistend and remove the ones for roby/syskit too 
(and/or extend roby/siskit) before walking thought all packages

Remarks: the testscripts should be adapted too, and of cource 
rock-create-orogen (i think this still created an "test-one")

-- 
  Dipl.-Inf. Matthias Goldhoorn
  Space and Underwater Robotic

  Universität Bremen
  FB 3 - Mathematik und Informatik
  AG Robotik
  Robert-Hooke-Straße 5
  28359 Bremen, Germany

  Tel.:     +49 421 178 45-4193
  Zentrale: +49 421 178 45-6550
  Fax:      +49 421 178 45-4150
  E-Mail:   matthias.goldhoorn at uni-bremen.de

  Weitere Informationen: http://www.informatik.uni-bremen.de/robotik



More information about the Rock-dev mailing list