Adding on to what Dave shared. From a quick Google the problem seems to be that the LLVM installer [1] on windows doesn't ship the "llvm-config" tool which meson uses to find the LLVM libraries. Looking at the build instructions [2] from Dave's link they are building LLVM from source presumably to
On Fri, 9 Feb 2024 at 14:38, Ashwin Bhat wrote:
>
> Hello,
>
> During Vulkanised 2024 I was super excited to hear and learn about Lavapipe
> https://vulkan.org/user/pages/09.events/vulkanised-2024/Vulkanised-2024-faith-ekstrand-collabora-Iago-toral-igalia.pdf
>
> Are there some basic tutorials
Hello Ashwin,
Hope you are doing well. I think the error that you mentioned is related
to the Clang version mismatch. You can use the following command to
configure desired clang version:
wget https://apt.llvm.org/llvm.sh
chmod u+x llvm.sh
./llvm.sh
here 'xx' should be the
Hello,
During Vulkanised 2024 I was super excited to hear and learn about Lavapipe
https://vulkan.org/user/pages/09.events/vulkanised-2024/Vulkanised-2024-faith-ekstrand-collabora-Iago-toral-igalia.pdf
Are there some basic tutorials on how to get started with setting up Lavapipe
swrast on
For what it's worth, I did raise this as a potential issue with the apache2
license migration for Khronos projects, and explicitly asked about MIT
dual-licensing at least for the GL headers. (The morbidly curious with a
Khronos membership may find the relevant discussion in the arb-nextgen
Ok, so the gist I'm getting is that it's impossible to use Vulkan
without using the official headers and loaders? It's just that I can't
see the Apache 2.0 license anywhere in the specification (single-page
html or pdf), so if I could re-implement those I would.
