check that it builds in isolation without --install

[dirk-thomas]

Currently several packages fail:

• urdfdom_headers: @dirk-thomas released 0.2.3-1
• eigen_stl_container: @dirk-thomas released 0.1.4-0
• tf: missing exported dependencies break downstream packages geometry#21
• nodelet_tutorial_math: lacks include directories when build in isolation without install common_tutorials#5 @dirk-thomas released 0.1.7-0
• laser_filters: missing dependency break isolated build without --install ros-perception/laser_filters#12
• fake_localization: fake_localization fails to build in isolation without --install ros-planning/navigation#93
• pcl_ros: missing exported dependency breaks downstream packages on hydro ros-perception/perception_pcl#27
• base_local_planner: base_local_planner fails to build in isolation without --install ros-planning/navigation#94
• pcl_ros

[dirk-thomas]

Steps to reproduce:

• Generate rosinstall file:
  • rosinstall_generator --rosdistro hydro desktop --deps > hydro-desktop.rosinstall
  • rosinstall_generator --rosdistro hydro desktop-full --deps > hydro-desktop-full.rosinstall
• Checkout all repos from one of the rosinstall files with wstool or vcs import
• ./src/catkin/bin/catkin_make_isolated

These are basically the plain install-from-source instruction but omitting the --install option.

[wjwwood]

@dirk-thomas The fix seems to be tagged in the repo:

https://github.com/ros/eigen_stl_containers
https://github.com/ros/eigen_stl_containers/blob/0.1.4/CMakeLists.txt

[tfoote]

All packages patched, closing.

[dirk-thomas]

@wjwwood pcl_ros has a new issue now:

DEPENDS on the catkin package 'message_filters' which must
therefore be listed as a run dependency in the package.xml

and

CATKIN_DEPENDS on itself...

[dirk-thomas]

The last pcl_ros issue has been fixed but...

Based on ros/catkin#483 I have to assume that testing for dry packages is currently broken. Therefore I would not recommend to call it a beta right now. I could not identify a clear way of fixing this issue - I will continue to look into this but that might take more than one day.

Probably the reason why we haven't experienced that until now is that we do have exactly 0 dry packages in hydro. (Does the dry release pipeline actually work for hydro?).

[tfoote]

I don't know of any problems with running the dry pipeline. There was one package released through it, but it's dependencies weren't met. Then it was catkinized, and delisted.

[dirk-thomas]

Are you sure about that?

The documentation (http://www.ros.org/wiki/release/Setup/Machine) still points to this repo:
https://code.ros.org/svn/ros/stacks/ros_release/trunk

I just assume that this is the file defining the distros (since it is the only location mentioning groovy):
https://code.ros.org/svn/ros/stacks/ros_release/trunk/rosdeb/src/rosdeb/targets.py

That would be a pretty good reason why we do not have any dry packages released for hydro...

[dirk-thomas]

I just tried a dry stack release with rosrelease-legacy which completed successfully. I did not try what the job generation or farm does with it though.