From: "Chip Davis" <cdavis@codeweavers.com>
Subject: Re: [PATCH] d3d12: Check for VK_KHR_external_fence_capabilities before using VkPhysicalDeviceIDProperties.
Message-Id: <962b177d5b82a8c6eab6c791c09703ec@codeweavers.com>
Date: Thu, 25 Feb 2021 17:14:57 +0000
In-Reply-To: <b4f5de27-003c-106d-e775-730a18a7f618@codeweavers.com>
References: <b4f5de27-003c-106d-e775-730a18a7f618@codeweavers.com> <20210224205842.591939-1-z.figura12@gmail.com> <CAOsNvwxQKv7s506JfJpYC6=bXUTqr0-FXrUm7YBOa05tT_3Ouw@mail.gmail.com> <a88451e6-5185-0c1d-0d7a-9ee91baf34d0@froggi.es> <4b8621f3-b9a8-0101-33aa-3b60c11ff0bc@codeweavers.com> <1ab2f18e-7b35-caf9-4af7-e0ff6c976233@froggi.es>

February 25, 2021 10:39 AM, "Zebediah Figura (she/her)" <zfigura@codeweavers.com> wrote:

> drivers whose latest
> versions are not accessible (e.g. the last version of MoltenVK that can
> be built for MacOS Mojave only supports Vulkan 1.0),

s/for/on

You should be able to *use* the resulting binary on Mojave.


Chip