| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I am working with ROS2 ardent, using Colcon to build.
The build is suceessful and I can also see my executable in <ws/build/package-name/build/lib/> but still when I run the package using ros2 run, no executables are found.
I found the problem.
In the setup.py file, I had a missing , for the last node in the entry pointsi.e.
entry_points={ 'console_scripts': [ 'listener = demo_nodes_py.topics.listener:main', 'talker = demo_nodes_py.topics.talker:main' 'listener_qos = demo_nodes_py.topics.listener_qos:main' ], },
NOTE : The missing `,` before the `listener_qos` node.
The strange thing here is, compiler compiles all the 3 nodes and I can see in the <ws/build/package-name/build/lib/> folder. Shouldnt the compiler just ignore the 3rd node listener_qos in this case ?
I have a mixed C++/Python package. To install a Python executable in this package, I've found it sufficient to do this:
my_package/scripts#!/usr/bin/env python3chmod +x__init__.py file in my_package/scriptsinstall(PROGRAMS scripts/my_python_file.py DESTINATION lib/${PROJECT_NAME} )
To me, this seems easier than what the tutorial recommends with setup.cfg and setup.py but maybe I'm missing something. Perhaps it's not Windows-compatible or something like that.
Here it is said to also use the following command pointing to the directory where the scripts are located (this might be necessary only for certain ROS2 distributions) before using the install(PROGRAMS...) command:
ament_python_install_package(my_package/scripts)
The making it executable step is really hard to notice. I had the same procedure from another site, but didn't make the python script executable. I could find the python script under install/my_pacakage/lib/my_pacakage/script.py but ros2 run my_pacakage script.py would throw No executable found
Asked: 2018-08-01 04:26:03 -0600
Seen: 6,814 times
Last updated: Jan 26 '22
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Did you source the setup.bash file in the install folder ??
source <ros2_ws>/install/setup.bashYou can add the command to ~/.bashrc so that you don't have to source every time you open a terminal.Yes, I have sourced the
setup.bashfile, stillno executable found