From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kalev Lember <klember@redhat.com>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/libopenh264: Drop openh264 runtime version checks
Date: Tue, 19 Dec 2023 00:15:29 +0200 (EET)
Message-ID: <2ce013ac-25de-1bb4-2870-949d30cb056@martin.st> (raw)
In-Reply-To: <20231209210731.201099-1-klember@redhat.com>
On Sat, 9 Dec 2023, Kalev Lember wrote:
> With the way the runtime checks are currently set up, every single
> openh264 release, no matter how minor, is considered an ABI break and
> requires ffmpeg recompilation. This is unnecessarily strict because it
> doesn't allow downstream distributions to ship any openh264 bug fix
> version updates without breaking ffmpeg's openh264 support.
>
> Years ago, at the time when ffmpeg's openh264 support was merged,
> openh264 releases were done without a versioned soname (the library was
> just libopenh264.so, unversioned). Since then, starting with version
> 1.3.0, openh264 has started using versioned sonames and the intent has
> been to bump the soname every time there's a new release with an ABI
> change.
>
> This patch drops the exact version check and instead adds a minimum
> requirement on 1.3.0 to the configure script.
>
> Signed-off-by: Kalev Lember <klember@redhat.com>
> ---
Thanks, pushed now!
// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-12-18 22:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 21:07 Kalev Lember
2023-12-18 22:15 ` Martin Storsjö [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 8:15 Kalev Lember
2023-12-08 8:39 ` Martin Storsjö
2023-12-08 11:49 ` Kalev Lember
2023-12-08 12:00 ` Martin Storsjö
2023-12-08 12:11 ` Kalev Lember
2023-12-08 12:17 ` Martin Storsjö
2023-12-08 15:48 ` Neal Gompa
2023-12-08 15:58 ` James Almer
2023-12-08 19:07 ` Kalev Lember
2023-12-08 19:12 ` James Almer
[not found] ` <66731BE2-B56B-4F28-80D6-D5599C76CD04@cosmin.at>
2023-12-08 19:12 ` Cosmin Stejerean via ffmpeg-devel
2023-12-08 20:03 ` Kalev Lember
2023-12-08 20:34 ` Martin Storsjö
2023-12-09 21:03 ` Kalev Lember
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=2ce013ac-25de-1bb4-2870-949d30cb056@martin.st \
--to=martin@martin.st \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=klember@redhat.com \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git