Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Dominik 'Rathann' Mierzejewski <dominik@greysector.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] warning about configuration mismatch between ff* binaries and libraries
Date: Mon, 11 Apr 2022 09:24:37 +0200
Message-ID: <YlPXtejcTTIBmiYO@sakura.greysector.net> (raw)
In-Reply-To: <tencent_9BE46BF603656A7A7DEEAE263991C219B50A@qq.com>

On Monday, 11 April 2022 at 05:15, "zhilizhao(赵志立)" wrote:
> > 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/9120e2cd3fadfa60269e94f97fc8107974c586fc
> > 
[...]
> > 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.

Granted.

> For the second question, I guess it may miss a few features depending
> on the configuration. Try `grep CONFIG_ -r fftools/` and test.

Thanks for the tip.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan
_______________________________________________
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".

  reply	other threads:[~2022-04-11  7:24 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 [this message]
2022-04-11  7:47   ` Anton Khirnov
2022-04-11 10:58     ` Nicolas George
2022-04-11 19:43     ` Soft Works

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=YlPXtejcTTIBmiYO@sakura.greysector.net \
    --to=dominik@greysector.net \
    --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