-
Notifications
You must be signed in to change notification settings - Fork 149
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
linking a non-catkin package #39
Comments
And did you solve it? |
@Gian-Alessio No. It seems not solvable. |
@HyHuang1995 I solved it for my case! I had an external library consisting of headers and a static library foo.a And it seems to work now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have an issue about linking a non-catkin package pangolin using catkin_simple. Since pangolin provides package.xml, intuitively I think it should work with catkin_simple. My catkin layout is set as merged. How I include pangolin in my package.xml is like:
And the compiling error with
catkin build my_pkg -j10
is like:It seems the headers are properly found, yet the
libpangolin.so
is not able to be linked.I had made it with another non-catkin package sophus, yet it can be used in a header-only manner. I guess there might be some subtlties.
I know it would work if I write a catkin wrapper for it, but I just wonder is there any generic way to include a non-catkin package?
Many thanks!
The text was updated successfully, but these errors were encountered: