From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: autodetect vulkan
Date: Mon, 20 Dec 2021 17:59:57 +0100
Message-ID: <20211220165957.GV2829255@pb2> (raw)
In-Reply-To: <MrMKbOp--3-2@lynne.ee>
[-- Attachment #1.1: Type: text/plain, Size: 1536 bytes --]
On Mon, Dec 20, 2021 at 11:15:08AM +0100, Lynne wrote:
> Recently, Metal support was merged, which is autodetected
> by default. Metal doesn't even have a hwcontext and it's not
> a hwaccel, nor would it likely ever be one as Apple won't drop
> videotoolbox.
>
> To keep it fair, autodetect Vulkan, which is a hwcontext,
> and for which there is an unmerged hwaccel patch.
>
> Patch attached.
>
> configure | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 09c6bfd367bd2ac897abc5716e2e9605341036cd 0001-configure-autodetect-vulkan.patch
> From 1f5243450242039f82a91e7eccb724af4b6ef37c Mon Sep 17 00:00:00 2001
> From: Lynne <dev@lynne.ee>
> Date: Mon, 20 Dec 2021 11:04:49 +0100
> Subject: [PATCH] configure: autodetect vulkan
breaks build here on ubuntu
./configure
ERROR: defined VK_VERSION_1_2 not satisfied
If you think configure made a mistake, make sure you are using the latest
version from Git. If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.
[....]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Old school: Use the lowest level language in which you can solve the problem
conveniently.
New school: Use the highest level language in which the latest supercomputer
can solve the problem without the user falling asleep waiting.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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".
next prev parent reply other threads:[~2021-12-20 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 10:15 Lynne
2021-12-20 10:44 ` Anton Khirnov
2021-12-20 13:07 ` Hendrik Leppkes
2021-12-20 16:59 ` Michael Niedermayer [this message]
2021-12-20 17:45 ` Lynne
2021-12-20 23:36 ` Michael Niedermayer
2021-12-21 7:05 ` "zhilizhao(赵志立)"
2021-12-21 11:31 ` Lynne
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=20211220165957.GV2829255@pb2 \
--to=michael@niedermayer.cc \
--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