From: James Almer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: James Almer <jamrial@gmail.com>
Subject: [FFmpeg-devel] Re: Consider using CMake.
Date: Sat, 24 Jan 2026 12:10:17 -0300
Message-ID: <69bf6487-3338-402f-9a10-eb3f0abb4547@gmail.com> (raw)
In-Reply-To: <c606d562-4913-4c26-acaf-f61ee90958fb@crueter.xyz>
[-- Attachment #1.1.1: Type: text/plain, Size: 1917 bytes --]
On 1/23/2026 7:47 PM, crueter via ffmpeg-devel wrote:
> Recently, I've been attempting to get FFmpeg building on MSVC. Normally
> FFmpeg is built with MinGW for Windows, but it is 100% possible to build
> it on MSVC. For those curious, I need this as a *static* library, and
> attempting to link statically built MinGW libraries on MSVC generally
> doesn't make for a fun time.
>
> However, previously I had to rely on several horrible hacks, such as
> running everything through the MSYS shell (not ideal in the slightest),
> and then manually implanting `cl.exe` and others into PATH. This is not
> only a huge pain, but actually caused significant problems as it made it
> much harder to make pretty much any changes whatsoever without
> inevitably breaking everything.
I'm fairly sure you're required to use an environment like Msys2 to
compile FFmpeg. Looking at
https://fate.ffmpeg.org/report.cgi?slot=amd64-msvc&time=20260123104905 i
see compiling statically with msvc is not a problem.
The configure script has plenty of msvc specific considerations. You may
have forgotten to to pass --toolchain=msvc to it.
>
> Thus, when I had to make some significant changes to my script, I ended
> up facing a large number of issues. In no particular order:
>
> * pkg-config is basically nonexistent on Windows, and is barely
> functional when it does exist. This was a problem for Vulkan,
> ffnvcodec, openssl, and others.
Every package we check for with pkg-config will have a .pc file on a
Windows install as it will on a Linux one. But i suspect quite a few
will require you to build them with mingw-w64, though.
Keep in mind that pkg-config requires you to pass --static to get the
proper command line arguments to link to dependencies statically. In the
context of ffmpeg configure, that'd be done with
--pkg-config-flags="--static".
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2026-01-24 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 22:47 [FFmpeg-devel] " crueter via ffmpeg-devel
2026-01-24 2:49 ` [FFmpeg-devel] " Timo Rothenpieler via ffmpeg-devel
2026-01-24 2:57 ` swurl via ffmpeg-devel
2026-01-24 16:06 ` Timo Rothenpieler via ffmpeg-devel
2026-01-24 18:38 ` crueter via ffmpeg-devel
2026-01-24 10:14 ` Rémi Denis-Courmont via ffmpeg-devel
2026-01-24 12:32 ` crueter via ffmpeg-devel
2026-01-24 16:13 ` Rémi Denis-Courmont via ffmpeg-devel
2026-01-25 17:33 ` swurl via ffmpeg-devel
2026-01-25 20:30 ` Rémi Denis-Courmont via ffmpeg-devel
2026-01-26 3:30 ` ff--- via ffmpeg-devel
2026-01-24 15:10 ` James Almer via ffmpeg-devel [this message]
2026-01-24 16:23 ` Zhao Zhili via ffmpeg-devel
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=69bf6487-3338-402f-9a10-eb3f0abb4547@gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=jamrial@gmail.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