From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] Tracking: FFmpeg 5.0
Date: Sun, 11 Dec 2022 19:07:19 +0100 [thread overview]
Message-ID: <20221211180719._Ksp5774puy8hTU_G5gbZA3ekRXWnF0okcpAK7KFAjg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36315@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
New comment by zlice on void-packages repository
https://github.com/void-linux/void-packages/pull/36315#issuecomment-1345620070
Comment:
Going down this rabbit hole as well (ffmpeg 5.1.2). So far the main blockers seem to be vlc, opencv/4, OpenSceneGraph/osg and OpenImageIO/OIIO (need gcc12? cmake fails to find pthread. Has a few deps as well).
My main concern is what to do about projects like ppsspp that seem to be unlikely to make changes for ffmpeg5?
next prev parent reply other threads:[~2022-12-11 18:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 13:45 [PR PATCH] " tibequadorian
2022-03-24 14:57 ` [PR PATCH] [Updated] " tibequadorian
2022-03-24 15:23 ` tibequadorian
2022-03-24 15:51 ` tibequadorian
2022-03-24 16:19 ` tibequadorian
2022-03-24 17:58 ` tibequadorian
2022-03-24 18:14 ` tibequadorian
2022-03-24 18:41 ` tibequadorian
2022-03-25 23:15 ` tibequadorian
2022-03-26 0:52 ` tibequadorian
2022-03-28 12:25 ` tibequadorian
2022-04-11 0:48 ` tibequadorian
2022-04-14 13:51 ` Idesmi
2022-04-14 14:11 ` tibequadorian
2022-04-14 14:58 ` [PR PATCH] [Updated] " tibequadorian
2022-04-21 13:26 ` marmeladema
2022-04-22 1:48 ` [PR PATCH] [Updated] " tibequadorian
2022-04-24 22:46 ` tibequadorian
2022-05-07 21:50 ` tibequadorian
2022-07-23 18:48 ` Idesmi
2022-10-22 2:14 ` github-actions
2022-11-06 2:13 ` [PR PATCH] [Closed]: " github-actions
2022-12-11 18:07 ` zlice [this message]
2022-12-11 20:18 ` paper42
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=20221211180719._Ksp5774puy8hTU_G5gbZA3ekRXWnF0okcpAK7KFAjg@z \
--to=zlice@users.noreply.github.com \
--cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).