Source: lz4
Version: 1.9.4-2
Severity: normal
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
* What led up to the situation?
Currently, liblz4-dev does not ship lz4Config.cmake which is
used to find LZ4 from CMake.
* What exactly did you do (or not do) that was effective (or
ineffective)?
It may be better to build lz4 package with CMake because
it contains build/cmake/CMakeLists.txt and it will ship
lz4Config.cmake.
build/cmake/CMakeLists.txt:
install(EXPORT lz4Targets
FILE lz4Targets.cmake
NAMESPACE LZ4::
DESTINATION ${LZ4_PKG_INSTALLDIR})
install(FILES
${CMAKE_CURRENT_BINARY_DIR}/lz4Config.cmake
${CMAKE_CURRENT_BINARY_DIR}/lz4ConfigVersion.cmake
DESTINATION ${LZ4_PKG_INSTALLDIR})
It may work with --buildsystem=cmake
--sourcedir=$(CURDIR)/build/cmake, but I'm not sure.
* What was the outcome of this action?
lz4Config.cmake is bundled for liblz4-dev.
* What outcome did you expect instead?
N/A
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.8.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8
(charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
