From: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Timo Rothenpieler <timo@rothenpieler.org>
Subject: [FFmpeg-devel] Re: Consider using CMake.
Date: Sat, 24 Jan 2026 03:49:03 +0100
Message-ID: <9ad166d0-4b2f-4067-9065-926bd1df191d@rothenpieler.org> (raw)
In-Reply-To: <c606d562-4913-4c26-acaf-f61ee90958fb@crueter.xyz>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 449 bytes --]
That's very unlikely to happen.
The current scripts support building using msvc just fine.
Porting everything to any other build system without causing an endless
slew of regressions and dropping support for a ton of targets is
virtually impossible.
Just open a MSVC command prompt, launch C:/MSYS64/msys2.exe (or wherever
you installed it) or if you got it set up wsl.exe, run ./configure
--toolchain=msvc and build away.
Timo
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3203 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 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 2:49 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 ` Timo Rothenpieler via ffmpeg-devel [this message]
2026-01-24 2:57 ` [FFmpeg-devel] " 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
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=9ad166d0-4b2f-4067-9065-926bd1df191d@rothenpieler.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=timo@rothenpieler.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