From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3] avcodec/mfenc: Dynamically load MFPlat.DLL
Date: Fri, 20 May 2022 23:05:13 +0300 (EEST)
Message-ID: <7b577e45-b12b-c5c-4ec7-10ac6963ef1@martin.st> (raw)
In-Reply-To: <c1020a63-6b9a-5182-fa42-65c17772078c@tytanium.xyz>
On Fri, 20 May 2022, Trystan Mata wrote:
> From 2bdef1bdb93efa40b7d3fe21270f9f23465bee90 Mon Sep 17 00:00:00 2001
> From: Trystan Mata <trystan.mata@tytanium.xyz>
> Date: Fri, 20 May 2022 14:26:49 +0200
> Subject: [PATCH] avcodec/mfenc: Dynamically load MFPlat.DLL
>
> Allow builds of FFmpeg with MediaFoundation to work under N editions of
> Windows which are without MediaFoundation by default.
>
> Signed-off-by: Trystan Mata <trystan.mata@tytanium.xyz>
> ---
> configure | 4 +-
> libavcodec/mf_utils.c | 26 +++++++------
> libavcodec/mf_utils.h | 16 ++++++--
> libavcodec/mfenc.c | 91 ++++++++++++++++++++++++++++++++++++-------
> 4 files changed, 107 insertions(+), 30 deletions(-)
This patch on its own breaks builds for UWP targets (where LoadLibrary
isn't available). Or more precisely, previously mfenc was enabled, now it
no longer is available.
For such targets, one can unconditionally assume that the functions are
available and can link directly against them. See ff_MFTEnumEx in
mf_utils.c how that's done so far. Doing the same instead of LoadLibrary
probably shouldn't be an issue for you, but I think we'd need to drop the
dependency on LoadLibrary in configure. (I think that's fine, we don't
really lose anything by doing that.)
Btw, when sending updates to an earlier posted patch, it'd be nice if
you'd mention somewhere what changed compared to the previous revision of
the patch.
// 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:[~2022-05-20 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 19:44 Trystan Mata
2022-05-20 20:05 ` Martin Storsjö [this message]
2022-05-20 20:48 ` Trystan Mata
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=7b577e45-b12b-c5c-4ec7-10ac6963ef1@martin.st \
--to=martin@martin.st \
--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