Bug#880438: libopencv-core-dev: installs headers in opencv2 directory
Control: close -1 On Thu, Jan 11, 2018 at 03:33:30PM +0100, Simon Frei wrote: > The digikam compiling issue was resolved on the spot back then. Glad to hear you solved your issue! > This report can be closed ACK, doing so. > thanks for your > explanation and sorry for wasting your time. no problem! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#880438: libopencv-core-dev: installs headers in opencv2 directory
I just stumbled upon these two different dir names when upgrading to opencv3 and assumed this was controlled by debian packaging and has been an oversight in the transition. The digikam compiling issue was resolved on the spot back then. This report can be closed - thanks for your explanation and sorry for wasting your time.
Bug#880438: libopencv-core-dev: installs headers in opencv2 directory
Control: tag -1 upstream moreinfo Control: severity -1 minor On Tue, Oct 31, 2017 at 03:28:14PM +0100, Simon Frei wrote: > All the headers files are placed below > /usr/include/opencv2/ > while libopencv-dev places its header files below > /usr/include/opencv/ > Apart from this inconsistency, I also don't see any reason for the > "reference" to version2 - I assume this was forgotten during the > transition? I believe that's some remnants from opencv 1 → 2 ages ago. At any rate, it's not a Debian thing, it's coming from upstream. > I detected this when trying to compile digikam (from upstream's source, not > the > deb), which did not detect the presence of opencv. That sounds weird. From what I can see Debian is not patching anything that should affect the place where headers are installed. Please double check your findings, but most probably you should raise this on the digikam side for doing wrong checks. If you suggest changing where opencv places its headers, please raise that on the upstream github project. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#880438: libopencv-core-dev: installs headers in opencv2 directory
Package: libopencv-core-dev Version: 3.2.0+dfsg-3 Severity: normal All the headers files are placed below /usr/include/opencv2/ while libopencv-dev places its header files below /usr/include/opencv/ Apart from this inconsistency, I also don't see any reason for the "reference" to version2 - I assume this was forgotten during the transition? I detected this when trying to compile digikam (from upstream's source, not the deb), which did not detect the presence of opencv. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopencv-core-dev depends on: ii libopencv-core3.2 3.2.0+dfsg-3 ii libtbb-dev 2017~U7-8 ii zlib1g-dev 1:1.2.8.dfsg-5 libopencv-core-dev recommends no packages. libopencv-core-dev suggests no packages. -- no debconf information
