colcon build in package source folders, how to avoid falling in this development mistake?
I am usually falling accidentally in the error of executing colcon build
inside a package source directory. This error ends up in a dirty directory tree with many build
and install
folders. This is very inconvenient, for example:
- You may think that your binary is updated when it really isnt
- Tools such as vscode works improperly in these conditions.
It is clear it is a human error. But in the past, when I used catkin_make
or catkin_tools
in ROS1 this issue was handled by the tool.
For example:
catkin build
could be executed anywhere inside the workspace but the generated items was properly generated inside ws/build
, ws/devel
and/or ws/install
folders.
Is there any way to make colcon smarter on this sense to help us not falling in this error? Do you have any "method" to help you to avoid this issue?
Asked by Pablo IƱigo Blasco on 2021-03-05 14:16:29 UTC
Answers
You may want to monitor and/or contribute to the issue tracking this feature request: https://github.com/colcon/colcon-core/issues/139
Asked by jdlangs on 2021-03-08 12:10:44 UTC
Comments