From: "Gonzalo Garramuño" <ggarra13@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Converting build to CMake
Date: Sun, 28 Aug 2022 20:31:12 -0300
Message-ID: <2fa910f1-324d-b1b8-5fff-d97d54ff488f@gmail.com> (raw)
In-Reply-To: <CADv_fo3o-3sybJ_r5iyhe+RY_vhaskmsGG5nqU-R1_r6x-ZZqQ@mail.gmail.com>
On 28/8/22 20:17, Jaime Rios wrote:
> Sorry if this has been asked before in the past.
>
> I am wondering if there has been any conversation around changing the
> current build setup of ffmpeg to CMake.
>
> The reason I ask is that I am not a fan of having to install MinGW just to
> build on Windows, and my experience so far with CMake has been a pleasant
> one, when having to build on multiple platforms (Windows/Linux/macOS).
>
> If there has been conversation about moving to CMake, where can I find the
> thread?
I would love that to happen myself too. The main issue is all the
dependencies that ffmpeg has to take care of. You need to have
FindLib*.cmake and/or BuldLib*cmake, plus you need to take care of which
libraries are open source, BSD, GPL, etc. and whether you need to locate
them with pkgconfig.
It is overall a lot of work, so something would need to get paid to do
so fulltime.
I have to wonder, as I only have Windows 8.1 so far, doesn't Windows 10
WSL2 solve the compilation issues by having the lib be compiled on an
Ubuntu distro?
--
Gonzalo Garramuño
ggarra13@gmail.com
_______________________________________________
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-08-28 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 23:17 Jaime Rios
2022-08-28 23:31 ` Gonzalo Garramuño [this message]
2022-08-29 0:25 ` Gerion Entrup
2022-08-29 5:15 ` Martijn van Beurden
2022-08-30 0:35 ` Jaime Rios
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=2fa910f1-324d-b1b8-5fff-d97d54ff488f@gmail.com \
--to=ggarra13@gmail.com \
--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