Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] configure: disable vulkan if min version insufficient
Date: Fri, 29 Sep 2023 21:26:49 +0200
Message-ID: <70dc80c2-7f78-4395-8991-240d79601fb5@rothenpieler.org> (raw)
In-Reply-To: <CAN8HRDkautj230i0eD5BJaLw-XukGpwcuHjG2rTt1-zVqNR-hw@mail.gmail.com>

On 29.09.2023 20:10, Tristan Matthews wrote:
> On Fri, Sep 29, 2023 at 1:37 PM Timo Rothenpieler <timo@rothenpieler.org> wrote:
>>
>> On 29.09.2023 15:52, Tristan Matthews wrote:
>>> Fixes: https://trac.ffmpeg.org/ticket/10596
>>> ---
>>>    configure | 3 ++-
>>>    1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/configure b/configure
>>> index 20db1801ed..50ba6f772f 100755
>>> --- a/configure
>>> +++ b/configure
>>> @@ -7154,7 +7154,8 @@ enabled crystalhd && check_lib crystalhd "stdint.h libcrystalhd/libcrystalhd_if.
>>>
>>>    if enabled vulkan; then
>>>        check_pkg_config_header_only vulkan "vulkan >= 1.3.255" "vulkan/vulkan.h" "defined VK_VERSION_1_3" ||
>>> -        check_cpp_condition vulkan "vulkan/vulkan.h" "defined(VK_VERSION_1_4) || (defined(VK_VERSION_1_3) && VK_HEADER_VERSION >= 255)"
>>> +        check_cpp_condition vulkan "vulkan/vulkan.h" "defined(VK_VERSION_1_4) || (defined(VK_VERSION_1_3) && VK_HEADER_VERSION >= 255)" ||
>>> +        warn "Disabling vulkan" && disable vulkan
>>>    fi
>>
>> Doesn't that just always disable vulkan if any of the previous checks
>> succeed? The logic looks weird to me.
> 
> No, it will only disable vulkan if all the previous checks fail as
> this conditional shortcircuits (so to get to here it would have to be
> false || false || false || false || false || warn "Disable vulkan" &&
> disable vulkan). If I hack the version number to match mine (changing
> it to 1.3.239), vulkan won't be disabled (that's why I added the
> warning message) and you'll hit the build breakage I and others are
> hitting currently.

My shell disagrees:

$ function warn() { echo $1; }
$ true || false || warn "Disabling vulkan" && echo DISABLED
DISABLED
$ false || true || warn "Disabling vulkan" && echo DISABLED
DISABLED
$ false || false || warn "Disabling vulkan" && echo DISABLED
Disabling vulkan
DISABLED
$ true || true || warn "Disabling vulkan" && echo DISABLED
DISABLED

No matter the results of the checks, this will always disable Vulkan, 
since the chain before it will always have a positive outcome, so && 
continues.
_______________________________________________
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:[~2023-09-29 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 13:52 Tristan Matthews
2023-09-29 17:37 ` Timo Rothenpieler
2023-09-29 18:10   ` Tristan Matthews
2023-09-29 19:26     ` Timo Rothenpieler [this message]
2023-09-29 20:09       ` Tristan Matthews
2023-09-29 18:32 ` Hendrik Leppkes
2023-09-29 19:06   ` Tristan Matthews

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=70dc80c2-7f78-4395-8991-240d79601fb5@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --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