Upgrade on ubuntu results in cmake error - no sdformat-9.5

Issue #30 resolved
Joshua created an issue

Ran sudo apt upgrade/update on ubuntu noetic.

Now have the following cmake error:

CMake Error at /opt/ros/noetic/share/velodyne_gazebo_plugins/cmake/velodyne_gazebo_pluginsConfig.cmake:113 (message):
  Project 'velodyne_gazebo_plugins' specifies '/usr/include/sdformat-9.5' as
  an include dir, which is not found.  It does neither exist as an absolute
  directory nor in '${{prefix}}//usr/include/sdformat-9.5'.  Check the issue
  tracker 'https://bitbucket.org/dataspeedinc/velodyne_simulator/issues' and
  consider creating a ticket if the problem has not been reported yet.
Call Stack (most recent call first):
  /opt/ros/noetic/share/catkin/cmake/catkinConfig.cmake:76 (find_package)
  CMakeLists.txt:6 (find_package)

Have tried clean build and reinstalling sdformat9 to no avail.

The current latest sdformat is 9.7 rather than 9.5 - if I use a symbolic link from sudo ln -s /usr/include/sdformat-9.7 /usr/include/sdformat-9.5 I no longer receive the error and the package runs correctly.

Comments (6)

  1. Kevin Hallenbeck

    I had a similar problem last week after a Gazebo update, but it was a compile error not a cmake configure error. The solution was to recreate the workspace (delete build and devel directories). A clean was not enough. Does that help?

  2. Kevin Hallenbeck

    It looks like velodyne_gazebo_plugins exports Gazebo’s include paths so dependent packages can find the includes, and the paths have changed since then due to a Gazebo and SDF update.

    I can re-trigger a build in the buildfarm, but it won’t get out until the next sync.

    Does your package need to find_package(catkin REQUIRED velodyne_gazebo_plugins) in its CMakeLists.txt? If not, you could remove it there and keep the dependency in package.xml.

  3. Joshua reporter

    It didn’t seem to fix the problem by deleting the build and devel dirs.

    I think your right - I don’t think it’s needed in the CMakeLists.txt.

    When is the next sync (ish)? It’s probably fine to wait for now.

  4. Log in to comment