Source: ebook-tools
Version: 0.2.2-4
Severity: wishlist
Tags: upstream
While looking at #739308 and its effect on other packages, I noticed that
cmake_libzip_zipconf_path.diff searches ${libdir} for zipconf.h.
libzip ships a pkg-config file, libzip.pc: it would be better to
use that, which should always result in use of the header and library
paths that the libzip upstream developer or Debian maintainer intend
to be used.
See also:
http://www.cmake.org/cmake/help/v3.0/module/FindPkgConfig.html
or if you (or the upstream developer) don't want to rely exclusively on
pkg-config,
http://www.cmake.org/Wiki/CMake:How_To_Find_Libraries#Writing_find_modules
(It might be worth asking the upstream developer of libzip whether
they consider their "build API" to be "you are expected to always use
pkg-config", like GLib and libdbus, or more like "pkg-config is an
optional convenience".)
Regards,
S
-- System Information:
Debian Release: jessie/sid
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
