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

github Action Binaries showing issue in find_package of cmake for image and opencv module #269

Closed
inbangsa opened this issue Oct 8, 2020 · 2 comments
Assignees

Comments

@inbangsa
Copy link
Collaborator

inbangsa commented Oct 8, 2020

Describe the bug
cmake find_package not able to find image and opencv module when using ifm3d binaries on windows.

To Reproduce
find_package(ifm3d 0.18.0 CONFIG
REQUIRED COMPONENTS image opencv
)

Expected behavior
.find package should work without showing the path issues for pcl and opencv libs

Output/Screenshots
CMake Error in CMakeLists.txt:
Imported target "ifm3d::image" includes non-existent path

"C:/deps/install/include/pcl-1.8"

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.

Configuration/Environment (please complete the following information):

  • OS: [Windows 10]
  • ifm3d version: [e.g. 0.18.0]
  • using ROS: [no]

Additional context
The issue is with Github Binary, cmake *-target.config files contains local path. This is case with Linux system also but issue is not found on Linux systems as dependent lib are install at pre-defined system path. on further investigation it is found that only headers of pcl and opencv are used and hence libraries are not linked to this image and opencv module making cmake appending the local path of build system in the generated cmake target config files.

@inbangsa inbangsa added the bug label Oct 8, 2020
@inbangsa inbangsa self-assigned this Oct 8, 2020
@github-actions
Copy link

github-actions bot commented Nov 9, 2022

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Nov 9, 2022
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

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

No branches or pull requests

1 participant