Making sense of a package with almost no files included
$ uname -a
Linux laptop 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
I need to use cv::face::createLBPHFaceRecognizer()
, which is not a part of the core OpenCV but rather a contributed module.
$ dpkg -l libopencv-contrib-dev
ii libopencv-contrib-dev:amd64 3.2.0+dfsg-6 amd64 development files for libopencv-contrib3.2
everything fine ... no:
src/cmd.cpp:150: error: ‘cv::face’ has not been declared
const auto model = cv::face::createLBPHFaceRecognizer();
^~~~
OK. Let's then include the needed headers manually:
$ dpkg -S libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/changelog.Debian.gz
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/copyright
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/README.Debian
Nothing! Is this a packager's mistake (this is Debian testing after all)? An OpenCV peculiarity? A minor oversight on my side? I would like to continue using the package manager, instead of compiling the whole thing myself.
package-management opencv
add a comment |
$ uname -a
Linux laptop 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
I need to use cv::face::createLBPHFaceRecognizer()
, which is not a part of the core OpenCV but rather a contributed module.
$ dpkg -l libopencv-contrib-dev
ii libopencv-contrib-dev:amd64 3.2.0+dfsg-6 amd64 development files for libopencv-contrib3.2
everything fine ... no:
src/cmd.cpp:150: error: ‘cv::face’ has not been declared
const auto model = cv::face::createLBPHFaceRecognizer();
^~~~
OK. Let's then include the needed headers manually:
$ dpkg -S libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/changelog.Debian.gz
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/copyright
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/README.Debian
Nothing! Is this a packager's mistake (this is Debian testing after all)? An OpenCV peculiarity? A minor oversight on my side? I would like to continue using the package manager, instead of compiling the whole thing myself.
package-management opencv
add a comment |
$ uname -a
Linux laptop 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
I need to use cv::face::createLBPHFaceRecognizer()
, which is not a part of the core OpenCV but rather a contributed module.
$ dpkg -l libopencv-contrib-dev
ii libopencv-contrib-dev:amd64 3.2.0+dfsg-6 amd64 development files for libopencv-contrib3.2
everything fine ... no:
src/cmd.cpp:150: error: ‘cv::face’ has not been declared
const auto model = cv::face::createLBPHFaceRecognizer();
^~~~
OK. Let's then include the needed headers manually:
$ dpkg -S libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/changelog.Debian.gz
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/copyright
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/README.Debian
Nothing! Is this a packager's mistake (this is Debian testing after all)? An OpenCV peculiarity? A minor oversight on my side? I would like to continue using the package manager, instead of compiling the whole thing myself.
package-management opencv
$ uname -a
Linux laptop 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
I need to use cv::face::createLBPHFaceRecognizer()
, which is not a part of the core OpenCV but rather a contributed module.
$ dpkg -l libopencv-contrib-dev
ii libopencv-contrib-dev:amd64 3.2.0+dfsg-6 amd64 development files for libopencv-contrib3.2
everything fine ... no:
src/cmd.cpp:150: error: ‘cv::face’ has not been declared
const auto model = cv::face::createLBPHFaceRecognizer();
^~~~
OK. Let's then include the needed headers manually:
$ dpkg -S libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/changelog.Debian.gz
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/copyright
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/README.Debian
Nothing! Is this a packager's mistake (this is Debian testing after all)? An OpenCV peculiarity? A minor oversight on my side? I would like to continue using the package manager, instead of compiling the whole thing myself.
package-management opencv
package-management opencv
edited 4 mins ago
Stephen Kitt
176k24401479
176k24401479
asked 14 mins ago
VoracVorac
1,03121834
1,03121834
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It was an oversight.
#include <opencv2/opencv.hpp>
#include <opencv2/face.hpp>
The first include is insufficient, the second one is needed as well.
Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S
.
add a comment |
The package is fine, you’re using the wrong dpkg
option:
dpkg -L libopencv-contrib-dev
will list all the files in the libopencv-contrib-dev
, which is what you’re after (and will show all the files listed here), whereas
dpkg -S libopencv-contrib-dev
searches all installed packages for files with libopencv-contrib-dev
in their path, which only matches the four files you’ve listed.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506660%2fmaking-sense-of-a-package-with-almost-no-files-included%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It was an oversight.
#include <opencv2/opencv.hpp>
#include <opencv2/face.hpp>
The first include is insufficient, the second one is needed as well.
Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S
.
add a comment |
It was an oversight.
#include <opencv2/opencv.hpp>
#include <opencv2/face.hpp>
The first include is insufficient, the second one is needed as well.
Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S
.
add a comment |
It was an oversight.
#include <opencv2/opencv.hpp>
#include <opencv2/face.hpp>
The first include is insufficient, the second one is needed as well.
Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S
.
It was an oversight.
#include <opencv2/opencv.hpp>
#include <opencv2/face.hpp>
The first include is insufficient, the second one is needed as well.
Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S
.
answered 14 mins ago
VoracVorac
1,03121834
1,03121834
add a comment |
add a comment |
The package is fine, you’re using the wrong dpkg
option:
dpkg -L libopencv-contrib-dev
will list all the files in the libopencv-contrib-dev
, which is what you’re after (and will show all the files listed here), whereas
dpkg -S libopencv-contrib-dev
searches all installed packages for files with libopencv-contrib-dev
in their path, which only matches the four files you’ve listed.
add a comment |
The package is fine, you’re using the wrong dpkg
option:
dpkg -L libopencv-contrib-dev
will list all the files in the libopencv-contrib-dev
, which is what you’re after (and will show all the files listed here), whereas
dpkg -S libopencv-contrib-dev
searches all installed packages for files with libopencv-contrib-dev
in their path, which only matches the four files you’ve listed.
add a comment |
The package is fine, you’re using the wrong dpkg
option:
dpkg -L libopencv-contrib-dev
will list all the files in the libopencv-contrib-dev
, which is what you’re after (and will show all the files listed here), whereas
dpkg -S libopencv-contrib-dev
searches all installed packages for files with libopencv-contrib-dev
in their path, which only matches the four files you’ve listed.
The package is fine, you’re using the wrong dpkg
option:
dpkg -L libopencv-contrib-dev
will list all the files in the libopencv-contrib-dev
, which is what you’re after (and will show all the files listed here), whereas
dpkg -S libopencv-contrib-dev
searches all installed packages for files with libopencv-contrib-dev
in their path, which only matches the four files you’ve listed.
answered 5 mins ago
Stephen KittStephen Kitt
176k24401479
176k24401479
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506660%2fmaking-sense-of-a-package-with-almost-no-files-included%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown