Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/6] ffmpeg: bump to version 4.1. ffserver is not supported anymore.
Date: Mon, 4 Feb 2019 11:20:52 +0100	[thread overview]
Message-ID: <20190204112052.284bbbea@windsurf> (raw)
In-Reply-To: <ea-mime-5c58064e-3d38-4e513c2d@www-5.netcourrier.com>

Hello,

On Mon,  4 Feb 2019 10:30:54 +0100 (CET)
lpdev at cordier.org wrote:

> > I'd like to hear from Bernd about this ffmpeg bump. If I remember well,
> > major ffmpeg bumps are typically breaking some APIs, causing build
> > issues with packages that use ffmpeg.
> 
> According to my experience with FFMpeg, API are marked as deprecated.
> They can still be used and linked correctly against all application.

Did you see the feedback from Bernd ? I know Bernd always forgets to Cc
people when replying, so make sure to check the mailing list for his
reply.

> However, the behaviour of the program can differ. What about creating
> a ffmpeg4 package, just like opencv2/3 packages?

Apparently, except for gstreamer1/gst1-libav that needs to be fixed for
ffmpeg 4.x, all other packages have already been fixed to work with
ffmpeg 4.x. So there is no reason to introduce a separate ffmpeg4
package. It would create more complexity/

> > If ffserver is no longer supported, we want to move this option to
> > Config.in.legacy so that users who have configurations with this
> > enabled are aware.
> 
> This does not appear in the official documentation. Would it be
> possible to add it?

Patches welcome ! :-)

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-02-04 10:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 12:15 [Buildroot] [PATCH v2 0/6] *** Add Intel QuickSync support to ffmpeg *** Louis-Paul Cordier
2019-01-31 12:15 ` [Buildroot] [PATCH v2 1/6] intel-gmmlib: new package Louis-Paul Cordier
2019-02-02 14:51   ` Thomas Petazzoni
2019-02-04  9:32   ` Thomas Petazzoni
2019-01-31 12:15 ` [Buildroot] [PATCH v2 2/6] intel-mediadriver: " Louis-Paul Cordier
2019-02-02 16:03   ` Thomas Petazzoni
2019-02-04  9:23     ` lpdev at cordier.org
2019-01-31 12:15 ` [Buildroot] [PATCH v2 3/6] intel-mediasdk: " Louis-Paul Cordier
2019-02-04  9:41   ` Thomas Petazzoni
2019-01-31 12:15 ` [Buildroot] [PATCH v2 4/6] ffmpeg: bump to version 4.1. ffserver is not supported anymore Louis-Paul Cordier
2019-02-02 14:54   ` Thomas Petazzoni
2019-02-03  8:48     ` Bernd Kuhls
2019-02-03 14:40       ` Peter Korsgaard
2019-02-04  9:39       ` Thomas Petazzoni
2019-02-04  9:30     ` lpdev at cordier.org
2019-02-04 10:20       ` Thomas Petazzoni [this message]
2019-01-31 12:15 ` [Buildroot] [PATCH v2 5/6] ffmpeg: enable Intel QuickSync support Louis-Paul Cordier
2019-01-31 12:15 ` [Buildroot] [PATCH v2 6/6] Update DEVELOPERS Louis-Paul Cordier
2019-02-02 14:47   ` Thomas Petazzoni
2019-02-04  9:11     ` lpdev at cordier.org
2019-02-04  9:43       ` Thomas Petazzoni
2019-02-04  9:48         ` lpdev at cordier.org

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=20190204112052.284bbbea@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