-
Notifications
You must be signed in to change notification settings - Fork 124
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
Installing to libexec with ament_cmake_auto #96
Comments
It would definitely be good if this CMake function would have an option to choose the install destination of the executables (either |
ok, so how about we change the default for executables to |
Ah, I noticed in the FHS standard that "Applications may use a single subdirectory under /usr/lib. If an application uses a subdirectory, all architecture-dependent data exclusively used by the application must be placed within that subdirectory." Does this then mean that if the executables are being installed to |
Libraries should still go into |
I think the key word there is "exclusively", so if you have a shared library that only your application uses, it would be put there. Since we mostly make things that could be reused by other packages, those shared libraries still belong in the top-level |
closed bu #97, thanks @wjwwood and @dirk-thomas for the input |
I have a ROS 2 package that uses
ament_cmake_auto
to take care of installing its libraries and executables (amcl)This causes the executables to be installed like this:
https://github.com/ament/ament_cmake/blob/dde5df8104073ff47aa96e482118adb6a03323f5/ament_cmake_auto/cmake/ament_auto_package.cmake#L62..L69
ROS 2 packages are currently being updated to install to "libexec" instead of bin.
Is it appropriate to add an option to
ament_cmake_auto
to install executables tolib/${PROJECT_NAME}
? It seems to be something that may be useful in other projects, but perhaps the functionality is too ROS-specific to belong in this package?The text was updated successfully, but these errors were encountered: