From: swurl via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
Cc: swurl <swurl@swurl.xyz>
Subject: [FFmpeg-devel] Re: Consider using CMake.
Date: Sun, 25 Jan 2026 12:33:56 -0500
Message-ID: <ac4908fa-e9ae-4cf8-8891-cf21cd91b73e@swurl.xyz> (raw)
In-Reply-To: <6458636.CO8ZRpQiV9@basile.remlab.net>
I probably should have expected stuck-up retards like you to immediately
complain about "just do it yourself harr harr harr". I specifically
created this to serve as a discussion piece, not for some 50 year old
corporate slave to immediately start hurling cope at me.
I actually did plan to port it eventually, but now I don't really feel
like doing it anymore because of your incredibly dismissive attitude
towards the mere thought of someone making an objectively good change.
Maybe I'll do it someday but add a clause to the license stating that
you must not be named Rémi Denis-Courmont to use this. :)
> rather than using a sorry approximation of one such as MSVC.
Again, unnecessarily dismissive. There are a huge number of use cases
for MSVC, because it is by far the most used compiler for desktop
targets. Do note that MinGW-built static libraries are not compatible
with MSVC executables.
On 1/24/26 11:13 AM, Rémi Denis-Courmont via ffmpeg-devel wrote:
> Le lauantaina 24. tammikuuta 2026, 14.32.39 Itä-Euroopan normaaliaika crueter
> via ffmpeg-devel a écrit :
>> Meson is even slower than the horribly written configure script AND has a
>> hard dependency on Python. Absolutely not.
> Ultimately you're free to port the FFmpeg build system to CMake yourself (or
> pay someone to do so), and submit a PR showing how so much better it actually
> is. Just don't be surprised if people reject it on the basis that it does not
> work or is no better, or even actually worse, for most purposes other than
> building FFmpeg on MSVC.
>
> By the way, that includes building FFmpeg for Windows with an actual C/C++
> toolchain (MingW or LLVM/Clang) from Linux or WSL, rather than using a sorry
> approximation of one such as MSVC.
>
> However your phrasing seems to indicate that you have no intention of actually
> conducting that work. So then, there is no point in continuing this
> discussion, because nobody else is going to try to do such it either.
>
_______________________________________________
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-25 17:34 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 [this message]
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=ac4908fa-e9ae-4cf8-8891-cf21cd91b73e@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