This repository has been archived by the owner on Jul 22, 2021. It is now read-only.
Install scripts properly in symlink installs #57
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
colcon build --symlink-install
, the installation method used for Python packages is different. It usespython setup.py develop
instead ofpython setup.py install
(see https://setuptools.readthedocs.io/en/latest/setuptools.html#development-mode). This requires a separate section in thesetup.cfg
file. Without it, the scripts get copied to the<install-prefix>/bin
directory instead of<install-prefix>/lib/<pkgname>
. They can be executed directly but will not work withros2 run
.The fix is to add a
develop
section tosetup.cfg
that specifies where scripts should be linked to when installing in development mode. See here for an example.