-
Notifications
You must be signed in to change notification settings - Fork 0
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
No absolute paths for dependants #3
base: master
Are you sure you want to change the base?
Changes from all commits
2b38125
fc6dc46
a434abe
8a538d6
bec613c
d5ced81
40c6b24
3fe58dc
f24142c
f657446
95a8929
a715655
4548c78
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,10 +20,3 @@ if(NOT TARGET SickLMS5xx::SickLMS5xx) | |
include("${CMAKE_CURRENT_LIST_DIR}/SickLMS5xxTargets.cmake") | ||
endif() | ||
|
||
# Have to come last as they modify some variable used above. | ||
include(CMakeFindDependencyMacro) | ||
find_dependency(Eigen3 3.3.4 REQUIRED) | ||
find_dependency(PCL 1.11 REQUIRED COMPONENTS common io) | ||
# link the deps so that client projects get them also | ||
target_link_libraries(SickLMS5xx::SickLMS5xx INTERFACE Eigen3::Eigen pcl_common pcl_io) | ||
target_include_directories(SickLMS5xx::SickLMS5xx INTERFACE $<INSTALL_INTERFACE:include>) | ||
Comment on lines
-23
to
-29
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it make sense to make the PCL links private as you did above, but the generated SickLMS5xxConfig.cmake should still have the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i had thought that gets executed when you call find_package(Sick), so there should not be any install paths in there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but this would be wrong. client projects need to include pcl include dirs if they want to make use of
pcl.hpp
shipped with this project.same with libs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the description of the PR, looks like it still produces the correct includes. Thing is we just cannot use absolute paths to where the includes "were" during install if it should be relocatable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where do you see the correct pcl dirs being included? did you try with pcl being in a different prefix than this library?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea its not in there, but if it contains a path which does not exist anymore, it errors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes no doubt, but I'm not sure what the fix is.