ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Catkin_make Error in ros-drivers / velodyne

asked 2021-06-23 06:39:31 -0500

ManChrys gravatar image

updated 2021-06-24 03:27:56 -0500

mgruhler gravatar image
  • OS and Version: Ubuntu 18.04
    • ROS Version: melodic

Hello guys,

I tried to install velodyne package following these steps

http://wiki.ros.org/velodyne/Tutorial...

but I have the following error

$rosdep install --from-paths src --ignore-src --rosdistro melodic -y

error the following packages/stacks could not have their rosdep keys resolved to system dependencies:
lio_sam: Cannot locate rosdep definition for [GTSAM]
rslidar_driver:Cannot locate rosdep definition for [rslidar_input]

error screenshot

Can anyone help me to solve this ?

Thanks in advance!

EDIT

If i catkin_make without velodyne's repo catkin_make works perfectly

Im trying to understand if the error above is the reason that i have the error in the catkin_make or not.

CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:11 (add_library):
  add_library cannot create target "driver_nodelet" because another target
  with the same name already exists.  The existing target is a shared library
  created in source directory
  "/home/geo/catkin_ws/src/ros_rslidar/rslidar_driver/src".  See
  documentation for policy CMP0002 for more details.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "velodyne_input" to target "driver_nodelet"
  which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/opt/ros/melodic/lib/libdiagnostic_updater.so"
  to target "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library
  "/opt/ros/melodic/lib/libdynamic_reconfigure_config_init_mutex.so" to
  target "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/opt/ros/melodic/lib/libnodeletlib.so" to
  target "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/opt/ros/melodic/lib/libbondcpp.so" to target
  "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/usr/lib/x86_64-linux-gnu/libuuid.so" to
  target "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/opt/ros/melodic/lib/libclass_loader.so" to
  target "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/usr/lib/libPocoFoundation.so" to target
  "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/usr/lib/x86_64-linux-gnu/libdl.so" to target
  "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/opt/ros/melodic/lib/libroslib.so" to target
  "driver_nodelet" which is not built in this directory.


CMake Error at velodyne/velodyne_driver/src/driver/CMakeLists.txt:13 (target_link_libraries):
  Attempt to add link library "/opt/ros/melodic/lib/librospack.so" to target
  "driver_nodelet" which is ...
(more)
edit retag flag offensive close merge delete

Comments

While I haven't pulled down the repo to get a better look, are you building anything extra inside of the catkin_ws that isn't from the velodyne repository? Those don't look like velodyne packages that are causing issues

404RobotNotFound gravatar image 404RobotNotFound  ( 2021-06-23 18:23:24 -0500 )edit

I second @404RobotNotFound this seems unrelated to velodyne, as the error message is from other packages (lio_sam and rslidar_driver to be specific). They are depending on other packages where there is no registered rosdep key, so you'd need those as source pacakges in your workspace.

mgruhler gravatar image mgruhler  ( 2021-06-24 01:07:14 -0500 )edit

Hello @404RobotNotFound,

yeah, of course I have more packages inside, because I work in more than one projects and with more than one lidars. It's first time though that I have that error when i catkin_make the workspace. Probably they have something common or something else, because until i git velodyne's repo catkin_make works perfectly.

ManChrys gravatar image ManChrys  ( 2021-06-24 01:12:10 -0500 )edit

@mgruhler hello my friend, is there any way this error be the reason for the catkin_make fail ?

ManChrys gravatar image ManChrys  ( 2021-06-24 01:14:39 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
2

answered 2021-06-24 03:50:37 -0500

mgruhler gravatar image

There are two unrelated errors:

  1. the rosdep install error: This is due to the packages lio_sam and rslidar_driver that exist in your workspace. The rosdep command will (most probably) also fail even without the velodyne repo in your workspace. The cause is that there are dependencies specified in the package.xml of those packages that are neither released ROS packages nor packages in your local workspace (i.e. GTSAM and rslidar_input).
  2. the CMake error: catkin builds everything in the same CMake context. Within one context, no two targets (added with add_executable, add_library or add_custom_target) can share the same name. You do have a target with same name in the velodyne package as well as in rslidar_driver, namely driver_nodelet (pretty obvious from the first cmake error message, the rest of the error messages is caused by the first). Possible solutions:
    1. build the workspace in isolation (using either catkin_make_isolated or catkin-tools)
    2. rename on of the targets such that there is no more nameclash
edit flag offensive delete link more

Comments

hmmm ok i see !!! Thank you my friend for the explanation!!

ManChrys gravatar image ManChrys  ( 2021-06-24 06:06:01 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2021-06-23 05:39:06 -0500

Seen: 393 times

Last updated: Jun 24 '21