From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v3 3/7] package/gstreamer1/gst1-libav: Fix build with FFmpeg 4.0
Date: Sun, 09 Sep 2018 16:16:09 +0200 [thread overview]
Message-ID: <9imf6fxkgr.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180908232331.0a5a634b@windsurf.home
Hello Thomas,
Am Sat, 08 Sep 2018 23:23:31 +0200 schrieb Thomas Petazzoni:
>> +Downloaded from https://bugs.gentoo.org/654628#c11
>
> I am a bit worried about this patch, see below.
>
>> +- params.padding = FF_INPUT_BUFFER_PADDING_SIZE;
>> ++ params.padding = AV_INPUT_BUFFER_PADDING_SIZE;
>
> Is AV_INPUT_BUFFER_PADDING_SIZE defined in ffmpeg 3.x that we
> currently have ? If not, then this change is going to break the build.
Yes, it was added to ffmpeg 2.8 back in 2015:
http://git.videolan.org/?
p=ffmpeg.git;a=commitdiff;h=29d147c94dd40a78ca3981f39365cc77dae9a0da
>> ++#if 0
>> + pspec = g_param_spec_float ("rc-qsquish", "Ratecontrol Limiting
Method",
>> + "0 means limit by clipping, otherwise use nice continuous
function",
>> + 0, 99.0f, 1.0f, G_PARAM_READWRITE | G_PARAM_STATIC_STRINGS);
>> + gst_ffmpeg_add_pspec (pspec, config.rc_qsquish, FALSE, mpeg, NULL);
>> ++#endif
>
> Is it OK to just remove all this code ?
To get gst1-libav 1.14.2 compiled, yes, it seems so.
The alternative would be to bump gstreamer1 to its current git master
branch like Debian did:
http://metadata.ftp-master.debian.org/changelogs//main/g/gst-libav1.0/gst-
libav1.0_1.15.0.1+git20180723+db823502-1_changelog
Regards, Bernd
next prev parent reply other threads:[~2018-09-09 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 7:31 [Buildroot] [PATCH/next v3 1/7] package/aubio: Fix build with FFmpeg 4.0 Bernd Kuhls
2018-08-25 7:31 ` [Buildroot] [PATCH/next v3 2/7] package/freeswitch: " Bernd Kuhls
2018-09-08 21:04 ` Thomas Petazzoni
2018-08-25 7:31 ` [Buildroot] [PATCH/next v3 3/7] package/gstreamer1/gst1-libav: " Bernd Kuhls
2018-09-08 21:23 ` Thomas Petazzoni
2018-09-09 14:16 ` Bernd Kuhls [this message]
2018-08-25 7:31 ` [Buildroot] [PATCH/next v3 4/7] package/mediastreamer: " Bernd Kuhls
2018-09-08 21:11 ` Thomas Petazzoni
2018-08-25 7:31 ` [Buildroot] [PATCH/next v3 5/7] package/motion: " Bernd Kuhls
2018-09-08 21:24 ` Thomas Petazzoni
2018-08-25 7:31 ` [Buildroot] [PATCH/next v3 6/7] package/squeezelite: " Bernd Kuhls
2018-09-08 21:26 ` Thomas Petazzoni
2018-08-25 7:31 ` [Buildroot] [PATCH/next v3 7/7] package/ffmpeg: bump version to 4.0.2 Bernd Kuhls
2018-09-08 21:27 ` Thomas Petazzoni
2018-09-08 21:04 ` [Buildroot] [PATCH/next v3 1/7] package/aubio: Fix build with FFmpeg 4.0 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=9imf6fxkgr.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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