-
Notifications
You must be signed in to change notification settings - Fork 16
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
Extra include folder pybind11_catkin causes issues #10
Comments
This is due to the need for all headers to be encapsulated in Is there a possible workaround you can think of? |
Modules created using the |
I agree that for distinguishing Bionic's system package and this ROS package, there should be a separate folder, otherwise /opt/ros/*/include would automatically override those system headers - even if the |
I suppose this would have to be done by a manually created |
If we agree on the approach, I can propose a PR. |
That would be wonderful, thank you very much for your time and effort. I agree that the hidden include in the macro is confusing. I wonder if moving the line using |
My idea was to adapt the |
I'm not sure why this package uses an extra layer
pybind11_catkin
in its include folder hierarchy, which is essentially skipped then by the macropybind_add_module
:https://github.com/ipab-slmc/pybind11_catkin/blob/2990ceed6522b0c61c700210714a120ca4abe959/cmake/pybind11_catkin.cmake.in#L19
This causes issues with catkin's normal mechanism to transitively pass upstream dependencies to downstream packages: While
catkin_INCLUDE_DIRS
will only contain the baseinclude
path, what is actually needed to find headers isinclude/pybind11_catkin
. However, this path is only provided in thepybind_add_module
macro, such that downstream packages will fail on corresponding includes.The text was updated successfully, but these errors were encountered: