When creating a setup.py file, setup.cfg can be used to specify some data in a declarative manner. But the logic in RosPackageIdentification.identify ignores the setup.py file if a setup.cfg file is specified.
This came up in an ugly way for my project which defines data_files in setup.py but defines some other package data in the setup.cfg file. When colcon attempts to install the project with --symlink-install option, it completely omits the package data, since it only looks at the cfg file.
When creating a setup.py file, setup.cfg can be used to specify some data in a declarative manner. But the logic in
RosPackageIdentification.identify
ignores thesetup.py
file if asetup.cfg
file is specified.This came up in an ugly way for my project which defines
data_files
insetup.py
but defines some other package data in thesetup.cfg
file. When colcon attempts to install the project with--symlink-install
option, it completely omits the package data, since it only looks at the cfg file.