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

generating message override python code from package #139

Open
asmodehn opened this issue Aug 2, 2017 · 3 comments
Open

generating message override python code from package #139

asmodehn opened this issue Aug 2, 2017 · 3 comments
Labels

Comments

@asmodehn
Copy link
Member

asmodehn commented Aug 2, 2017

Using catkin_pip_package() with generate_message() actually breaks.

What happens (as of catkin_pip 0.2.2) is :

  • msg and srv are created in devel/lib/python2.7/dist-packages with an empty __init__.py
  • the ros1-pip-template.egg-link file is created in devel/lib/python2.7/site-packages

The link in the egg-link file seems to be checked after the path in PYTHONPATH (likely following default python handling of sys.path), and the package is found with an empty __init__.py, then it only contains msg and srv and not the code...

This is in practice not happening often, as people have taken the habit to split messages into a separate specific package (maybe for similar reasons ?). However we should support this properly, as catkin officially supports it.

@asmodehn asmodehn added the bug label Aug 2, 2017
@asmodehn
Copy link
Member Author

asmodehn commented Aug 2, 2017

Note : catkin itself also seems buggy with message generation.

Doing, in a ros pacakge source :

$ mkdir build
$ cmake .. -DCMAKE_INSTALL_PREFIX=./install

detects the messages and services, but the python class are never generated...

This might be related and we need to dig and investigate more...

@asmodehn
Copy link
Member Author

asmodehn commented Aug 2, 2017

Or it might be because the message generation actually happens when running "make" after that, and not during cmake config step...

@asmodehn
Copy link
Member Author

asmodehn commented Aug 3, 2017

Note this might be mixed with the fact that a namespace package would make this work (message subpackage in one directory and module code in another_, but a usual python2 package would not...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant