Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix binary install location #40

Merged
merged 2 commits into from
Feb 4, 2023
Merged

Fix binary install location #40

merged 2 commits into from
Feb 4, 2023

Conversation

Tobias-Fischer
Copy link
Contributor

Hi @traversaro,

This should fix RoboStack/ros-humble#41

It definitely fixes the demo_nodes_py issue that you have referred to in that issue. Are you aware of any packages that do not have a setup.cfg, so we can test this case as well?

@traversaro
Copy link
Member

It definitely fixes the demo_nodes_py issue that you have referred to in that issue. Are you aware of any packages that do not have a setup.cfg, so we can test this case as well?

I am not aware of any!

@Tobias-Fischer
Copy link
Contributor Author

Ok - in this case, I think it’s best to throw an error if there is no setup.cfg as the PKG_NAME is the full name including ros-humble which is not what we want.

@Tobias-Fischer Tobias-Fischer merged commit a1e74dc into master Feb 4, 2023
@Tobias-Fischer Tobias-Fischer deleted the fix-install-location branch August 9, 2023 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nodes from pure python packages can't be started via ros2 run on Linux
2 participants