From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] warning about configuration mismatch between ff* binaries and libraries
Date: Mon, 11 Apr 2022 19:43:34 +0000
Message-ID: <DM8P223MB03656D03C0F4C9233D4F6348BAEA9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <164966324395.21047.9390028368945689627@lain.red.khirnov.net>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Anton Khirnov
> Sent: Monday, April 11, 2022 9:47 AM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] warning about configuration mismatch
> between ff* binaries and libraries
>
> Quoting zhilizhao(赵志立) (2022-04-11 05:15:59)
> >
> >
> > > On Apr 11, 2022, at 5:31 AM, Dominik 'Rathann' Mierzejewski
> <dominik@greysector.net> wrote:
> > >
> > > Dear Developers!
> > > I'm curious about the warning about configuration mismatch between
> ff*
> > > binaries and the libraries introduced in:
> > >
> > >
> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/9120e2cd3fadfa60269e94
> f97fc8107974c586fc
> > >
> > > At Fedora, we're interested in having two builds: one built with
> limited
> > > set of codecs[1] that is legally distributable in the US (since
> Red Hat,
> > > Fedora sponsor is a US-based company) and another, with a more
> complete
> > > set of codecs[2] distributed by RPM Fusion. The builds are
> intended to
> > > be drop-in replacements. We'd like to be able to distribute just
> one set
> > > of ff* binaries and only have two different interchangeable builds
> of
> > > libraries.
> > >
> > > The idea is to have the builds differ by enabled codecs only and
> have
> > > the rest of the configuration the same (even if it's not the case
> > > today).
> > >
> > > So, does that warning still make sense today? Will something break
> > > if we swap the libraries but keep the binary on user systems?
> >
> > That’s exactly an example of why the warning is useful. Otherwise
> user can
> > be confused why some codecs are missing while banner says they are
> enabled
> > by configure. So yes, the warning still make sense.
>
> I would prefer to not show all that noise in the banner, which would
> also resolve the confusion. Build information should be reduced to
> loglevel verbose IMO.
I agree and I would suggest reconsidering James' earlier patch for this.
softworkz
_______________________________________________
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".
prev parent reply other threads:[~2022-04-11 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 21:31 Dominik 'Rathann' Mierzejewski
2022-04-11 3:15 ` "zhilizhao(赵志立)"
2022-04-11 7:24 ` Dominik 'Rathann' Mierzejewski
2022-04-11 7:47 ` Anton Khirnov
2022-04-11 10:58 ` Nicolas George
2022-04-11 19:43 ` Soft Works [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=DM8P223MB03656D03C0F4C9233D4F6348BAEA9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/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