Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: rcombs <rcombs@rcombs.me>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH 1/7] configure: fix setting OBJCCFLAGS
Date: Tue, 21 Dec 2021 18:07:19 -0600
Message-ID: <20211222000725.38266-1-rcombs@rcombs.me> (raw)

We call this OBJCFLAGS in help text, but common.mak looks for OBJCCFLAGS.
---
 configure | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure b/configure
index 3abc4428e5..d49457d192 100755
--- a/configure
+++ b/configure
@@ -7643,7 +7643,7 @@ LN_S=$ln_s
 CPPFLAGS=$CPPFLAGS
 CFLAGS=$CFLAGS
 CXXFLAGS=$CXXFLAGS
-OBJCFLAGS=$OBJCFLAGS
+OBJCCFLAGS=$OBJCFLAGS
 ASFLAGS=$ASFLAGS
 NVCCFLAGS=$nvccflags
 AS_C=$AS_C
-- 
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".

             reply	other threads:[~2021-12-22  0:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22  0:07 rcombs [this message]
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 ` [FFmpeg-devel] [PATCH 5/7] configure: test the metal compiler before use rcombs
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-1-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