Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gerion Entrup <gerion.entrup@flump.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Converting build to CMake
Date: Mon, 29 Aug 2022 02:25:40 +0200
Message-ID: <2449991.aRYC9UBvo8@gump> (raw)
In-Reply-To: <2fa910f1-324d-b1b8-5fff-d97d54ff488f@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1441 bytes --]

Am Montag, 29. August 2022, 01:31:12 CEST schrieb Gonzalo Garramuño:
> 
> 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?

There is a (maintained) fork of FFMpeg with Meson (similar to CMake):
https://gitlab.freedesktop.org/gstreamer/meson-ports/ffmpeg

However, this has nothing to do with the original project (AFAIK).

Best,
Gerion


[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

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

  reply	other threads:[~2022-08-29  0:25 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
2022-08-29  0:25   ` Gerion Entrup [this message]
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=2449991.aRYC9UBvo8@gump \
    --to=gerion.entrup@flump.de \
    --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