On Wed, Dec 29, 2010 at 8:51 AM, Jack O'Quin <jack.oquin@gmail.com> wrote:
> On Wed, Dec 29, 2010 at 1:40 AM, Ken Conley <kwc@willowgarage.com> wrote:
>
>> Pretty much.  As a quicker test, r-grepping for a package name in the
>> source is usually a good sniff test.  Also keep in mind that roslaunch
>> files create implicit dependencies, so 'make' is often not a
>> sufficient test -- though the fastidious can use the
>> rosbuild_add_roslaunch_check() macro:
>>
>> http://www.ros.org/wiki/rosbuild/CMakeLists#rosbuild_add_roslaunch_check
>
> Does that actually check the dependencies? I thought it just did a parse check.

It does static analysis of the file and fails on any issues that it finds, e.g.:

 * missing package
 * missing node
 * missing depends
 * other config errors

 - Ken


> Don't forget another useful tool, that lists any missing dependencies
> generated by a set of launch files:
>
>  $ roslaunch-deps -w file.launch
>
>  http://www.ros.org/wiki/roslaunch/Commandline%20Tools#roslaunch-deps
> --
>  joq
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>