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

CMake Error when linking GazeboYARPPlugins libraries #643

Closed
HosameldinMohamed opened this issue Jan 13, 2023 · 3 comments · Fixed by #644
Closed

CMake Error when linking GazeboYARPPlugins libraries #643

HosameldinMohamed opened this issue Jan 13, 2023 · 3 comments · Fixed by #644

Comments

@HosameldinMohamed
Copy link
Contributor

When trying to build a plugin that uses some of the libraries of gazebo-yarp-plugins. Following http://robotology.github.io/gazebo-yarp-plugins/master/use_as_library.html

I get the following error when generating CMake:

 CMake Error in software/gazebo/plugins/vive-transform-plugin/CMakeLists.txt:
   Imported target "GazeboYARPPlugins::gazebo_yarp_lib_common" includes
   non-existent path

     "/home/hosameldin/code/robotology-superbuild/build/install/include/include"

   in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

   * The path was deleted, renamed, or moved to another location.

   * An install or uninstall procedure did not complete successfully.

   * The installation package was faulty and references files it does not
   provide.

However, the build goes through with no errors.

I thought it was worth reporting it anyways.

@HosameldinMohamed
Copy link
Contributor Author

CC @traversaro

@traversaro
Copy link
Member

Indeed, there is a bug in the CMake script. If you are compiling gazebo-yarp-plugins from source, can you check if #644 solves the problem? Thanks!

@traversaro
Copy link
Member

I thought it was worth reporting it anyways.

Thanks!

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 a pull request may close this issue.

2 participants