0
$\begingroup$

In ROS1 we could modify XML launchfile and roslaunch them directly without catkin_make rebuilding, in ROS2 it seems if I modify python launchfile, I need to rebuild the package otherwise

ros2 launch <package_name> <launchfile_name>

runs the old launchfile. Do I need to rebuild the package after each modification or am I missing something?

Improve this question
$\endgroup$

1 Answer 1

Reset to default
3
$\begingroup$

You can use the --symlink-install flag while building your code. This will create symlinks in the install directory which points to actual source files rather then creating copies. So whenever you make change in your source files it will automatically be reflected in install and you won't be required to build again. You can also check this link, what is the use of --symlink-install in ROS2 colcon build?, for further help.

Improve this answer
$\endgroup$
1
  • $\begingroup$ Thanks, I mindlessly removed that option without reading what it does 😅 $\endgroup$
    – Martin
    Commented Mar 6 at 11:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.