Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v5 4/6] package/ffmpeg: add optional support for opencv
Date: Fri, 26 Aug 2016 21:46:51 +0200	[thread overview]
Message-ID: <20160826214651.136a994b@free-electrons.com> (raw)
In-Reply-To: <1471273421-12076-4-git-send-email-bernd.kuhls@t-online.de>

Hello,

On Mon, 15 Aug 2016 17:03:39 +0200, Bernd Kuhls wrote:
> ffmpeg only needs the imgproc module of opencv:
> https://github.com/FFmpeg/FFmpeg/commit/15708f13477aaf2effdc0d7fc727507bc468335a
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>

Applied to next. However: what about opencv3 support?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-08-26 19:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 15:03 [Buildroot] [PATCH/next v5 1/6] package/ffmpeg: bump to version 3.1.2 Bernd Kuhls
2016-08-15 15:03 ` [Buildroot] [PATCH/next v5 2/6] package/ffmpeg: default to --cpu=generic for MIPS architecture Bernd Kuhls
2016-08-26 19:46   ` Thomas Petazzoni
2016-08-15 15:03 ` [Buildroot] [PATCH/next v5 3/6] package/ffmpeg: re-enable for mips64r2 and mips64r6 Bernd Kuhls
2016-08-26 19:46   ` Thomas Petazzoni
2016-08-15 15:03 ` [Buildroot] [PATCH/next v5 4/6] package/ffmpeg: add optional support for opencv Bernd Kuhls
2016-08-26 19:46   ` Thomas Petazzoni [this message]
2016-08-27  6:06     ` Bernd Kuhls
2016-08-15 15:03 ` [Buildroot] [PATCH/next v5 5/6] package/tvheadend: remove compat patch for ffmpeg < 3.x Bernd Kuhls
2016-08-26 19:46   ` Thomas Petazzoni
2016-08-15 15:03 ` [Buildroot] [PATCH/next v5 6/6] package/vlc: add support for ffmpeg 3.0 Bernd Kuhls
2016-08-26 19:47   ` Thomas Petazzoni
2016-08-26 19:45 ` [Buildroot] [PATCH/next v5 1/6] package/ffmpeg: bump to version 3.1.2 Thomas Petazzoni

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=20160826214651.136a994b@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