From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] opencv: cleanup depends and comments
Date: Thu, 6 Feb 2014 09:59:54 +0100 [thread overview]
Message-ID: <20140206095954.143a94ea@skate> (raw)
In-Reply-To: <20140205223406.275A79C67A@busybox.osuosl.org>
Dear Peter Korsgaard,
On Wed, 5 Feb 2014 23:33:41 +0100, Peter Korsgaard wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=5f7cbb264ec21f75320ad8518d27f4c605c825f8
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> Since the opencv package globally depends on BR2_TOOLCHAIN_HAS_THREADS
> and BR2_USE_WCHAR, then cleanup these redundant (and useless)
> dependencies in the opencv's sub-options.
>
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/opencv/Config.in | 12 ++----------
> 1 files changed, 2 insertions(+), 10 deletions(-)
Is this really our policy? It was mentioned several times that we
should probably keep those, so that if the OpenCV package option itself
no longer needs wchar or threads in the future, we already have those
dependencies needed for the packages selected by OpenCV.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-06 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 22:33 [Buildroot] [git commit] opencv: cleanup depends and comments Peter Korsgaard
2014-02-06 8:59 ` Thomas Petazzoni [this message]
2014-02-06 9:04 ` Thomas De Schampheleire
2014-02-06 22:14 ` Peter Korsgaard
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=20140206095954.143a94ea@skate \
--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