What is the manifest.xml convention for dependencies of launch files?

asked 2011-10-27 06:00:34 -0500

Asomerville
2743 ●74 ●99 ●133 http://www.resquared.com/

updated 2011-11-23 19:49:42 -0500

5904 ●43 ●74 ●102 http://www.informatik....

Often times packages will build libraries and executables that have certain dependencies, and then related launch files that often pull in more dependencies.

Depending on perspective, the launch file deps could be thought of as non-essential. With that perspective, one might seek to minimize dependencies and leave them out of the manifest.

This is not simply an academic question, since, for example, many python scripts call to roslib.load_manifest which will throw an exception if a package is missing even if it's not strictly necessary.

What is considered to be "best practice" in this situation?

edit retag flag offensive close merge delete

add a comment

6

answered 2011-10-27 06:56:47 -0500

Patrick Mihelich
4336 ●32 ●37 ●44

You should include launch file dependencies in the manifest. In cases where this is undesirable, split the launch files out into a separate package. For example, openni_launch has more dependencies than the openni_camera driver package.

edit flag offensive delete link

add a comment

1

answered 2011-10-27 06:03:02 -0500

bhaskara
1479 ●15 ●24 ●32

I'd leave the dependencies in, personally. It means 'rosmake my_package' will have the postcondition that all launch files can now be run, at the expense of a few extra entries in the include/import paths.