You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However this can be a bad match for CMake since, pip install actually takes care of the equivalent of :
creating a workspace (wstool)
checking out all your source dependencies at the correct revision (vcstools/git/svn/...)
retrieve all binary dependencies at the correct version (> rosdep/deb/rpm/...)
which is not traditionally related with CMake ( if we except the more recent ExternalProject feature )
This can lead to confusions, like "why do we need to modify the source tree? Everything should be in the build tree to be able to clean up."
Maybe this feature will be better integrated with another ROS tool ?
The text was updated successfully, but these errors were encountered:
Currently catkin_pip requirements does a
pip install -r requirements.txt
like so : https://github.com/pyros-dev/catkin_pip/blob/devel/cmake/catkin-pip-requirements.cmake.in#L32However this can be a bad match for CMake since, pip install actually takes care of the equivalent of :
which is not traditionally related with CMake ( if we except the more recent ExternalProject feature )
This can lead to confusions, like "why do we need to modify the source tree? Everything should be in the build tree to be able to clean up."
Maybe this feature will be better integrated with another ROS tool ?
The text was updated successfully, but these errors were encountered: