Groovy xml updating
To maintain compatibility with software which has a dependency on the stack name, you need to make a new catkin package which is a “metapackage”.This package has the same name as the stack and contains no source code, only a list of dependencies containing all the packages which used to be in the stack.For example, say our old stack was named “stick” and it had 2 packages: “pickage” and “peckage”.The directories would look like this: Note that the for stick has a buildtool depend on catkin.To understand why, we need to understand where Smart Things code is executed.
Because of the nature of Smart Apps and Device Handlers, and the various methods available to you, the need to create your own classes or object structures is rarely needed.
In groovy, it was decided to instead drop the notion of stacks (for metapackages), and make packages the atomic unit of build.
The names of the templates for the environment hooks for devel space and installspace have been unified.
To update an already catkinized ROS stack from the Fuerte-version of catkin to Groovy the following steps are necessary: The version of Catkin for ROS groovy does not support the idea of a “stack” of packages which get wrapped up together into a Debian (or similar) installable package.
Instead, catkin packages now get built into separate installable Debian (or similar) packages.