fixed: No libarchiveConfig.cmake file after build and install with th… #1912
Conversation
|
@bradking - does this look reasonable to you? I'm not that familiar with CMake installation conventions. |
|
It would be nice for upstream libarchive to provide a proper CMake Package Configuration file. However, projects can only rely on it if all libarchive installations reliably provide it. The change proposed here will provide it only for distributions that use CMake to build libarchive itself. Those using the autotools build system for libarchive will not provide it. Since CMake already comes with builtin support for |
| @@ -264,6 +264,8 @@ IF(ENABLE_INSTALL) | |||
| RUNTIME DESTINATION bin | |||
| LIBRARY DESTINATION lib | |||
| ARCHIVE DESTINATION lib) | |||
| INSTALL(TARGETS archive archive_static | |||
| EXPORT libarchive_target) | |||
There was a problem hiding this comment.
CMake already comes with a builtin FindLibArchive module that is used to implement find_package(LibArchive) calls. If upstream libarchive does start providing a CMake package, it should provide the same LibArchive::LibArchive target name that the find module does to help projects transition. Some internal refactoring of libarchive's CMake build system may be helpful to match target names.
using cmake to build and install, No libarchiveConfig.cmake file is in prefix directory.
Fixed: libarchiveConfig.cmake Will be in ${PREFIX}/share/cmake/Libarchive/ directory