Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: swurl via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Cc: swurl <swurl@swurl.xyz>
Subject: [FFmpeg-devel] Re: Consider using CMake.
Date: Fri, 23 Jan 2026 21:57:51 -0500
Message-ID: <38c0a55d-dc09-43ab-a557-71c9add742c7@swurl.xyz> (raw)
In-Reply-To: <9ad166d0-4b2f-4067-9065-926bd1df191d@rothenpieler.org>

"MSVC works fine! Just go to MSYS2 first"

That isn't "working", that's a horrible workaround. Not to mention this 
is a nightmare to script or run in a CI environment.

Again, *I have tried this and it isn't good.* It's very prone to 
breaking and pretty much impossible to make any meaningful changes. Not 
to mention it almost never works

 > 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.

Call me crazy but I don't think FFmpeg needs to support somebody's 2003 
toaster running a 200 MHz POWER4. Everything else is trivial to keep 
support for, because *CMake literally runs everywhere.* See 
https://cmake.org/cmake/help/latest/variable/CMAKE_SYSTEM_NAME.html.

On 1/23/26 9:49 PM, Timo Rothenpieler via ffmpeg-devel wrote:
> 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
>
> _______________________________________________
> ffmpeg-devel mailing list --ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email toffmpeg-devel-leave@ffmpeg.org
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2026-01-24 15:59 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 [this message]
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=38c0a55d-dc09-43ab-a557-71c9add742c7@swurl.xyz \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=swurl@swurl.xyz \
    /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