From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v2 1/1] package/kodi: switch to internal ffmpeg version 3.1.11 build
Date: Tue, 14 Aug 2018 15:53:34 +0200 [thread overview]
Message-ID: <20180814155334.0376e758@windsurf> (raw)
In-Reply-To: <20180812202352.15128-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 12 Aug 2018 22:23:52 +0200, Bernd Kuhls wrote:
> Kodi 17 is incompatible with ffmpeg-4.x. To prepare the ffmpeg bump we
> switch the current Kodi package to internally build and statically link
> to patched ffmpeg-3.1.11 provided by upstream. Gnutls is added as
> dependency to allow playback of https streams.
>
> Upstream expects Kodi 17 to be used with ffmpeg 3.1.x (see upstream PR
> 12368) so we choose the upstream way to build ffmpeg instead of provi-
> ding a version choice for ffmpeg in buildroot.
>
> This commit can be reverted when Kodi is bumped to version 18, currently
> released as alpha3.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> v2:
> - git-formatted patches (Thomas)
> - fixed pkgconf problem by adding PKG_CONFIG_SYSROOT_DIR instead
> of using /usr/bin/pkg-config (Thomas)
> - added upstream patch to fix ffmpeg build error on mips
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-14 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 20:23 [Buildroot] [PATCH/next v2 1/1] package/kodi: switch to internal ffmpeg version 3.1.11 build Bernd Kuhls
2018-08-14 13:53 ` Thomas Petazzoni [this message]
2018-08-14 13:56 ` 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=20180814155334.0376e758@windsurf \
--to=thomas.petazzoni@bootlin.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