[rosrun] Couldn't find executable named

asked 2019-02-19 02:27:08 -0500

Jägermeister gravatar image

updated 2019-02-19 02:40:00 -0500

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 ...
(more)
edit retag flag offensive close merge delete

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 with source ~/ros_ws/devel/setup.bash inside current terminal session.

Dyson sphere gravatar image Dyson sphere  ( 2019-02-19 02:37:56 -0500 )edit

I added the CMakeLists.txt. Also, ROS_PACKAGE_PATH points to /home/user/ros_ws/src:/opt/ros/melodic/share, isn't this okay?

Jägermeister gravatar image Jägermeister  ( 2019-02-19 02:41:24 -0500 )edit

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/1669...EDIT: can you uncomment CATKIN_DEPENDS pcl_conversions pcl_ros roscpp sensor_msgs line

Dyson sphere gravatar image Dyson sphere  ( 2019-02-19 02:58:00 -0500 )edit

No solution there for my case, unfortunately. I also tried adding set(EXECUTABLE_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/bin) but nope.

Jägermeister gravatar image Jägermeister  ( 2019-02-19 03:04:31 -0500 )edit

can you try echo $CMAKE_PREFIX_PATH. Just checked my setup and this one points to my workspace/devel

Dyson sphere gravatar image Dyson sphere  ( 2019-02-19 03:21:25 -0500 )edit

That outputs /home/user/ros_ws/devel:/opt/ros/melodic

Jägermeister gravatar image Jägermeister  ( 2019-02-19 03:23:18 -0500 )edit

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

Dyson sphere gravatar image Dyson sphere  ( 2019-02-19 03:32:20 -0500 )edit

They are not inside /devel no, just as I expected, it's not even being built.

Jägermeister gravatar image Jägermeister  ( 2019-02-19 03:36:02 -0500 )edit