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

can't compile on catkin with kindr and kindr_ros masters #16

Open
mcamurri opened this issue Nov 14, 2017 · 1 comment
Open

can't compile on catkin with kindr and kindr_ros masters #16

mcamurri opened this issue Nov 14, 2017 · 1 comment

Comments

@mcamurri
Copy link

mcamurri commented Nov 14, 2017

If I clone the latest masters of kindr and kindr ros

and try to compile both in my catkin workspace, I get the following error:

CMake Error at /opt/ros/kinetic/share/catkin/cmake/catkin_workspace.cmake:95 (message):
  This workspace contains non-catkin packages in it, and catkin cannot build
  a non-homogeneous workspace without isolation.

If I try to compile kindr_ros as caktin package and I install kindr normally (i.e. mkdir build && cd build && cmake .. && sudo make install), I can compile kindr_ros as cmake project but not as a catkin project, because I get:

CMake Warning at kindr_ros/kindr_ros/CMakeLists.txt:11 (find_package):
  Found package configuration file:

    /usr/local/share/kindr/cmake/kindrConfig.cmake

  but it set kindr_FOUND to FALSE so package "kindr" is considered to be NOT
  FOUND.

then the project fails because kindr does not generate a kindr.pc file anymore.

If I add the following line to the kindrConfig.cmake.in it works again:

set(kindr_FOUND true)

Any idea why? Why do the file sets only kindr_FOUND_CATKIN_PROJECT and not kindr_FOUND if catkin does not detect it?

I'm using Kinetic with Ubuntu 16.04.

Thanks,
Marco.

mcamurri pushed a commit to mcamurri/kindr that referenced this issue Nov 14, 2017
This is to prevent catkin from detecting the file but setting it as NOT FOUND (see ANYbotics/kindr_ros#16)
@mcamurri
Copy link
Author

This has been automatically closed because it is accidentally referenced in a merge request which is not correlated to the issue.

@pfankhauser pfankhauser reopened this Mar 13, 2018
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

No branches or pull requests

2 participants