[rosrun] Couldn't find executable named
I am facing the good old Couldn't find executable
error yet again, and I have no idea why is this happening. I followed the PCL tutorial from the ROS page, did exactly the same, copy-pasted even, still, it's not working.
I have these two lines in my CMakeLists.txt:
add_executable(example src/example.cpp)
target_link_libraries(example ${catkin_LIBRARIES})
and I have these in my package.xml:
<build_depend>libpcl-all-dev</build_depend>
<exec_depend>libpcl-all</exec_depend>
and these are in my .bashrc:
#source /opt/ros/melodic/setup.bash
source ~/ros_ws/devel/setup.bash
Whether or not I comment in the first line, doesn't matter, I always end up with the same error.
[rosrun] Couldn't find executable named example below /home/user/ros_ws/src/my_pcl_tutorial
What's wrong?
EDIT: Here is the CMakeLists.txt file:
cmake_minimum_required(VERSION 2.8.3)
project(my_pcl_tutorial)
## Compile as C++11, supported in ROS Kinetic and newer
# add_compile_options(-std=c++11)
## Find catkin macros and libraries
## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz)
## is used, also find other catkin packages
find_package(catkin REQUIRED COMPONENTS
pcl_conversions
pcl_ros
roscpp
sensor_msgs
)
## System dependencies are found with CMake's conventions
# find_package(Boost REQUIRED COMPONENTS system)
## Uncomment this if the package has a setup.py. This macro ensures
## modules and global scripts declared therein get installed
## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html
# catkin_python_setup()
################################################
## Declare ROS messages, services and actions ##
################################################
## To declare and build messages, services or actions from within this
## package, follow these steps:
## * Let MSG_DEP_SET be the set of packages whose message types you use in
## your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...).
## * In the file package.xml:
## * add a build_depend tag for "message_generation"
## * add a build_depend and a exec_depend tag for each package in MSG_DEP_SET
## * If MSG_DEP_SET isn't empty the following dependency has been pulled in
## but can be declared for certainty nonetheless:
## * add a exec_depend tag for "message_runtime"
## * In this file (CMakeLists.txt):
## * add "message_generation" and every package in MSG_DEP_SET to
## find_package(catkin REQUIRED COMPONENTS ...)
## * add "message_runtime" and every package in MSG_DEP_SET to
## catkin_package(CATKIN_DEPENDS ...)
## * uncomment the add_*_files sections below as needed
## and list every .msg/.srv/.action file to be processed
## * uncomment the generate_messages entry below
## * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...)
## Generate messages in the 'msg' folder
# add_message_files(
# FILES
# Message1.msg
# Message2.msg
# )
## Generate services in the 'srv' folder
# add_service_files(
# FILES
# Service1.srv
# Service2.srv
# )
## Generate actions in the 'action' folder
# add_action_files(
# FILES
# Action1.action
# Action2.action
# )
## Generate added messages and services with any dependencies listed here
# generate_messages(
# DEPENDENCIES
# sensor_msgs
# )
################################################
## Declare ROS dynamic reconfigure parameters ##
################################################
## To declare and build dynamic reconfigure parameters within this
## package, follow these steps:
## * In the file package.xml:
## * add a build_depend and a exec_depend tag for "dynamic_reconfigure"
## * In this file (CMakeLists.txt):
## * add "dynamic_reconfigure" to
## find_package(catkin REQUIRED COMPONENTS ...)
## * uncomment the "generate_dynamic_reconfigure_options" section below
## and list every .cfg file to be processed
## Generate dynamic reconfigure parameters in the 'cfg' folder
# generate_dynamic_reconfigure_options(
# cfg/DynReconf1.cfg
# cfg/DynReconf2.cfg
# )
###################################
## catkin specific configuration ##
###################################
## The catkin_package macro generates cmake config files for your package
## Declare things to be passed to dependent projects
## INCLUDE_DIRS: uncomment this if your package contains header files
## LIBRARIES: libraries you create in this project that dependent projects also need
## CATKIN_DEPENDS: catkin_packages dependent projects also need
## DEPENDS: system dependencies of this project that dependent projects also need
catkin_package(
# INCLUDE_DIRS include
# LIBRARIES my_pcl_tutorial
# CATKIN_DEPENDS pcl_conversions pcl_ros roscpp sensor_msgs
# DEPENDS system_lib
)
###########
## Build ##
###########
## Specify additional locations of header files
## Your package locations should be listed before other locations
include_directories(
# include
${catkin_INCLUDE_DIRS}
)
add_executable(example src/example.cpp)
target_link_libraries(example ${catkin_LIBRARIES})
## Declare a C++ library
# add_library(${PROJECT_NAME}
# src/${PROJECT_NAME}/my_pcl_tutorial.cpp
# )
## Add cmake target dependencies of the library
## as an example, code may need to be generated before libraries
## either from message generation or dynamic reconfigure
# add_dependencies(${PROJECT_NAME} ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
## Declare a C++ executable
## With catkin_make all packages are built within a single CMake context
## The recommended prefix ensures that target names across packages don't collide
# add_executable(${PROJECT_NAME}_node src/my_pcl_tutorial_node.cpp)
## Rename C++ executable without prefix
## The above recommended prefix causes long target names, the following renames the
## target back to the shorter version for ease of user use
## e.g. "rosrun someones_pkg node" instead of "rosrun someones_pkg someones_pkg_node"
# set_target_properties(${PROJECT_NAME}_node PROPERTIES OUTPUT_NAME node PREFIX "")
## Add cmake target dependencies of the executable
## same as for the library above
# add_dependencies(${PROJECT_NAME}_node ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
## Specify libraries to link a library or executable target against
# target_link_libraries(${PROJECT_NAME}_node
# ${catkin_LIBRARIES}
# )
#############
## Install ##
#############
# all install targets should use catkin DESTINATION variables
# See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html
## Mark executable scripts (Python etc.) for installation
## in contrast to setup.py, you can choose the destination
# install(PROGRAMS
# scripts/my_python_script
# DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
# )
## Mark executables and/or libraries for installation
# install(TARGETS ${PROJECT_NAME} ${PROJECT_NAME}_node
# ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
# LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
# RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
# )
## Mark cpp header files for installation
# install(DIRECTORY include/${PROJECT_NAME}/
# DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION}
# FILES_MATCHING PATTERN "*.h"
# PATTERN ".svn" EXCLUDE
# )
## Mark other files for installation (e.g. launch and bag files, etc.)
# install(FILES
# # myfile1
# # myfile2
# DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
# )
#############
## Testing ##
#############
## Add gtest based cpp test target and link libraries
# catkin_add_gtest(${PROJECT_NAME}-test test/test_my_pcl_tutorial.cpp)
# if(TARGET ${PROJECT_NAME}-test)
# target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME})
# endif()
## Add folders to be run by python nosetests
# catkin_add_nosetests(test)
Asked by Jägermeister on 2019-02-19 03:27:08 UTC
Comments
Can you show the whole CMakeLists file? Also did you open a new terminal session after building? .bashrc is invoked when you open a new session or manually with
source ~/.bashrc
. You can also source the setup.bash directly withsource ~/ros_ws/devel/setup.bash
inside current terminal session.Asked by Dyson sphere on 2019-02-19 03:37:56 UTC
I added the
CMakeLists.txt
. Also,ROS_PACKAGE_PATH
points to/home/user/ros_ws/src:/opt/ros/melodic/share
, isn't this okay?Asked by Jägermeister on 2019-02-19 03:41:24 UTC
that seems to be ok, but the executable shouldn't be in the file he is looking, rather in build and devel. Any luck with this answer: https://answers.ros.org/question/166926/rosrun-executable-not-found/ EDIT: can you uncomment
CATKIN_DEPENDS pcl_conversions pcl_ros roscpp sensor_msgs
lineAsked by Dyson sphere on 2019-02-19 03:58:00 UTC
No solution there for my case, unfortunately. I also tried adding
set(EXECUTABLE_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/bin)
but nope.Asked by Jägermeister on 2019-02-19 04:04:31 UTC
can you try
echo $CMAKE_PREFIX_PATH
. Just checked my setup and this one points to my workspace/develAsked by Dyson sphere on 2019-02-19 04:21:25 UTC
That outputs
/home/user/ros_ws/devel:/opt/ros/melodic
Asked by Jägermeister on 2019-02-19 04:23:18 UTC
The only thing I can suggest at this moment is to look manually if your executables are inside devel, try re-building once more and sourcing manually your devel/setup.bash
Asked by Dyson sphere on 2019-02-19 04:32:20 UTC
They are not inside
/devel
no, just as I expected, it's not even being built.Asked by Jägermeister on 2019-02-19 04:36:02 UTC
Do you build using catkin_make, and if so can you find your executables if there are any?
Asked by Dyson sphere on 2019-02-19 21:31:27 UTC
Yes I build using that command, and I can't find this particular one there. It doesn't build this specific project.
Asked by Jägermeister on 2019-02-20 06:41:30 UTC
Hello @Jägermeister did you finally figure it out ? I have a similar problem
Asked by edote on 2020-06-16 07:59:12 UTC