From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] package/opencv: module objdetect depends on imgproc
Date: Mon, 18 Apr 2016 22:21:59 +0200 [thread overview]
Message-ID: <20160418222159.166e2790@free-electrons.com> (raw)
In-Reply-To: <CAHXCMM+gkMR16KjCW=-2o0vw_0tXDmB931ZbVk1t=WwEOPj7+A@mail.gmail.com>
Hello,
On Mon, 18 Apr 2016 21:57:49 +0200, Samuel Martin wrote:
> > Can you comment on this one? I thought we had no expression of the
> > interdependencies between OpenCV modules. Are those interdependencies
> > build-time dependencies or run-time dependencies?
> In opencv(2) we don't, in opencv3 we do.
>
> I did the work on opencv3 when bumping the package, but did not take
> the time to do it on opencv(2) after we reverted it.
>
> These interdependencies are build-time deps., they are already
> expressed in the cmake code.
> One just needs to extract the info and report it in the Config.in.
> I'll check if I can quickly dig up something about this on the
> opencv(2) package.
If they are already expressed in the CMake code, the build will not
fail, so why did you object to the previous iteration of Bernd's patch?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-18 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 15:11 [Buildroot] [PATCH v2 1/2] package/freeswitch: mod_cv needs BR2_PACKAGE_OPENCV_LIB_OBJDETECT Bernd Kuhls
2016-04-18 15:11 ` [Buildroot] [PATCH v2 2/2] package/opencv: module objdetect depends on imgproc Bernd Kuhls
2016-04-18 19:20 ` Thomas Petazzoni
2016-04-18 19:57 ` Samuel Martin
2016-04-18 20:07 ` Bernd Kuhls
2016-04-18 20:21 ` Thomas Petazzoni [this message]
2016-04-18 21:18 ` Samuel Martin
2016-04-18 21:24 ` Samuel Martin
2016-04-18 21:28 ` Thomas Petazzoni
2016-04-18 21:38 ` Samuel Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160418222159.166e2790@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox