From: rcombs <rcombs@rcombs.me>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH 5/7] configure: test the metal compiler before use
Date: Tue, 21 Dec 2021 18:07:23 -0600
Message-ID: <20211222000725.38266-5-rcombs@rcombs.me> (raw)
In-Reply-To: <20211222000725.38266-1-rcombs@rcombs.me>
Apparently Metal.framework is included with the command line tools
(and thus may be present without Xcode), but the Metal compiler is only
included as part of Xcode.
---
configure | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configure b/configure
index 06a4d3f485..cb02c54bf1 100755
--- a/configure
+++ b/configure
@@ -6365,6 +6365,8 @@ enabled videotoolbox && {
check_func_headers CoreVideo/CVImageBuffer.h kCVImageBufferTransferFunction_SMPTE_ST_428_1 "-framework CoreVideo"
}
+enabled metal && test_cmd $metalcc -v || disable metal
+
check_struct "sys/time.h sys/resource.h" "struct rusage" ru_maxrss
check_type "windows.h dxva.h" "DXVA_PicParams_AV1" -DWINAPI_FAMILY=WINAPI_FAMILY_DESKTOP_APP -D_CRT_BUILD_DESKTOP_APP=0
--
2.33.1
_______________________________________________
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-22 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 0:07 [FFmpeg-devel] [PATCH 1/7] configure: fix setting OBJCCFLAGS rcombs
2021-12-22 0:07 ` [FFmpeg-devel] [PATCH 2/7] configure: fix .d generation for C++ and Obj-C files rcombs
2021-12-22 0:07 ` [FFmpeg-devel] [PATCH 3/7] lavfi/metal: don't use braced-include for internal headers rcombs
2021-12-22 0:07 ` [FFmpeg-devel] [PATCH 4/7] configure: ensure we use the macOS SDK's metal compiler by default rcombs
2021-12-22 0:07 ` rcombs [this message]
2021-12-22 0:07 ` [FFmpeg-devel] [PATCH 6/7] lavfi/metal: fix build on pre-10.15 SDKs rcombs
2021-12-22 0:07 ` [FFmpeg-devel] [PATCH 7/7] lavfi/metal: fix build with pre-10.11 deployment targets rcombs
2021-12-22 1:20 ` Aman Karmani
2022-01-27 18:32 ` Alex
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=20211222000725.38266-5-rcombs@rcombs.me \
--to=rcombs@rcombs.me \
--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