-
Notifications
You must be signed in to change notification settings - Fork 68
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
Make sure to ament_export_libraries. #73
Conversation
ament_export_libraries() ends up generating a setup.sh file for each library that exports LD_LIBRARY_PATH. This is important when building in isolated mode so that downstream consumers of the libraries can find the library at runtime. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
Seems a bit redundant to export the interfaces AND the libraries. Should ament be adding |
Will need a PR over in ecl_lite too. |
It's a good question, I don't know the answer. It's probably worth bringing up in |
Oops, yeah. I had to do fixes over there too, PR upcoming. |
As brought in, in PR 73 #73 Reported in ament/ament_cmake#132 And fixed in https://github.com/ament/ament_cmake/pull/135/files
As brought in, in PR 73 stonier/ecl_core#73 Reported in ament/ament_cmake#132 And fixed in https://github.com/ament/ament_cmake/pull/135/files
* [infra] rever the workaround (PR #73) for interface library exports Hitherto would cause a problem on builds with isolated installs, so you are supposed to explicitly state the target name, refer to - ament/ament_cmake#132 - https://github.com/ament/ament_cmake/pull/135/files Colcon/bouncy doesn't reproduce our earlier problems since it exports all of the appropriate paths regardless. This however, should be the right fix.
ament_export_libraries() ends up generating a setup.sh file
for each library that exports LD_LIBRARY_PATH. This is
important when building in isolated mode so that downstream
consumers of the libraries can find the library at runtime.
Signed-off-by: Chris Lalancette clalancette@openrobotics.org