Tool information
Virtual environments affected
Note that the Ubuntu versions can probably be dealt with via a simple apt-get, but the Mac and Windows environments require running an interactive installer.
Can this tool be installed during the build?
Uncertain. It's possible that the installer has an unattended mode that can be used but I've never tried to do so. Some components included in the SDK (such as the SPIRV tooling) can be acquired via other means, such as using vcpkg to install the spirv-tools library. However, it's worth noting that the vcpkg port for Vulkan specifically says
Due to the complexity involved, this package doesn't install the Vulkan SDK.
It instead verifies that Vulkan is installed.
Other packages can depend on this package to declare a dependency on Vulkan.
Indicating that building the VulkanSDK from source is extremely non-trivial
Are you willing to submit a PR?
I'm uncertain what a PR could accomplish in this area, since the installation of the SDK is typically a manual process. But sure, I'll submit a PR if someone can provide guidance on a mechanism and within my ability to fix.
I was able to install it on windows during my builds with the following:
- name: Setup Vulkan
run: |
Invoke-WebRequest -Uri "https://sdk.lunarg.com/sdk/download/1.1.126.0/windows/VulkanSDK-1.1.126.0-Installer.exe" -OutFile VulkanSDK.exe
$installer = Start-Process -FilePath VulkanSDK.exe -Wait -PassThru -ArgumentList @("/S");
$installer.WaitForExit();
It takes 2-2.5 minutes to run.
This issue has not had any activity for 45 days and will be closed in 45 days if there continues to be no activity.
Considering this can be installed as suggested above and maintenance could be an issue if we bake it in the environment, we won't add it. Thanks for suggesting it @jherico .
That's a bit unsatisfying. I only shared a way to install it on windows, each other platform will have a different install process, and it can take up to 30% of my entire job (4 of 12 minute) so it's eating a ton of my monthly minutes. The time is a bit inconsistent, though, I've seen as low as 1 minute, but average seems to be 3 minutes looking at some historical builds.
I think it should be added too. At least the tools and lib/include files. The solution @kudaba mentioned didn't work for me, it succeeded but the %VULKAN_SDK% variable wasn't set on completion and therefore it couldn't compile for me.
Most helpful comment
That's a bit unsatisfying. I only shared a way to install it on windows, each other platform will have a different install process, and it can take up to 30% of my entire job (4 of 12 minute) so it's eating a ton of my monthly minutes. The time is a bit inconsistent, though, I've seen as low as 1 minute, but average seems to be 3 minutes looking at some historical builds.