From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/linphone: remove ffmpeg-related patches
Date: Mon, 18 Dec 2017 10:00:24 +0100 [thread overview]
Message-ID: <20171218100024.05e1b6f3@windsurf> (raw)
In-Reply-To: <20171217135346.925-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 17 Dec 2017 14:53:46 +0100, Bernd Kuhls wrote:
> The linphone package never provided video support.
>
> While this commit
> https://git.buildroot.net/buildroot/commit/package/linphone?id=dec04466549cd40e2696ae7725e90d6559bee640
>
> added support for ffmpeg 3.0+ the next commit, which fixed the build of
> the bundled mediastreamer2 library, added --disable-video:
> https://git.buildroot.net/buildroot/commit/package/linphone?id=f3492b28d89c1f2448c9662a6f755cb48e8c0f0b
>
> At this point the ffmpeg 3.0 patches could have been removed because
> ffmpeg is only used if video support is enabled:
>
> https://github.com/BelledonneCommunications/mediastreamer2/blob/6c2a608800a221942f2a827e0abb60346e7d065f/acinclude.m4#L80
> https://github.com/BelledonneCommunications/mediastreamer2/blob/6c2a608800a221942f2a827e0abb60346e7d065f/acinclude.m4#L107
>
> This patch catches up on that to avoid changing the upstream URL for
> the patches which is broken.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> v2: removed unneeded ffmpeg patches instead of using
> http://snapshot.debian.org/archive/debian/20161118T211932Z/pool/main/l/linphone
> as proposed by Thomas.
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-12-18 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 13:53 [Buildroot] [PATCH v2 1/1] package/linphone: remove ffmpeg-related patches Bernd Kuhls
2017-12-18 9:00 ` Thomas Petazzoni [this message]
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=20171218100024.05e1b6f3@windsurf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.