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
Hi there. First of all, congratulations for this tool, it works excellent and it is incredibly useful.
I have found a specific use case in one of my projects, and I do not know how to better handle it using colcon tool.
Case
I have a github repository with folders inside, each of them is a cmake colcon package (with its CMakeLists.txt, its package.xml, etc.) (for example, check this repository of ROS2 https://github.com/ros2/rclcpp).
My problem here is that I have several files that are going to be used in ALL or several of the packages. i.e. LICENSE file, VERSION file, some .cmake common files, etc.
Question
Can I handle this shared files in a way that I do not have to maintain copied files?
Possible solutions
These are the solutions I have thought about so far, but any of them seems like "completly correct" for me:
Copy the file in every subdirectory needed. This causes a gigantic redundancy, and the modification in each shared file must be copied to the rest of the files.
Use symbolic links. This do not work with windows, as the creation of symlinks needs administrator rights, so the Github repository will be broken.
Use a new colcon package only to hold these shared files. This does not seems right, as it adds a dependency and a new colcon package that is just a hotchpotch package.
Colcon feature
I do not think this is a strange use case (having into account the package distribution in ROS2 repositories), and maybe colcon could add a tool or a way of handling this.
Maybe, a possibility was to create a kind of package that could contain subpackages. This way, subpackages are installed independently and could be found by external packages, but at the same time, some CMake variables could be set from the parent "superproject", avoiding copy of files.
The text was updated successfully, but these errors were encountered:
Hi there. First of all, congratulations for this tool, it works excellent and it is incredibly useful.
I have found a specific use case in one of my projects, and I do not know how to better handle it using colcon tool.
Case
I have a github repository with folders inside, each of them is a cmake colcon package (with its
CMakeLists.txt
, itspackage.xml
, etc.) (for example, check this repository of ROS2 https://github.com/ros2/rclcpp).My problem here is that I have several files that are going to be used in ALL or several of the packages.
i.e.
LICENSE
file,VERSION
file, some.cmake
common files, etc.Question
Can I handle this shared files in a way that I do not have to maintain copied files?
Possible solutions
These are the solutions I have thought about so far, but any of them seems like "completly correct" for me:
Colcon feature
I do not think this is a strange use case (having into account the package distribution in ROS2 repositories), and maybe
colcon
could add a tool or a way of handling this.Maybe, a possibility was to create a kind of package that could contain subpackages. This way, subpackages are installed independently and could be found by external packages, but at the same time, some CMake variables could be set from the parent "superproject", avoiding copy of files.
The text was updated successfully, but these errors were encountered: