Qt5 Vulkan
-
wrote on 31 Aug 2021, 18:17 last edited by
Is there a way to enable Vulkan using the Windows installer? Or do you have to manually include it when building from source?
Note: I got the Vulkan SDK (1.2.182.0) from LunarG and have the VULKAN_SDK set to the correct path.
-
Hi and welcome to devnet,
Based on the documentation of QVulkanWindow you should only need to install the SDK on Windows.
What is your current issue ?
Did you try one of the Vulkan example ? -
wrote on 31 Aug 2021, 21:48 last edited by
It appears Qt can't find the necessary Vulkan headers, since its symbols are marked as unknown. Is it possible to see where Qt is looking for these headers? Or does it only use VULKAN_SDK?
-
Did you try to build one of Qt's Vulkan examples ?
-
wrote on 1 Sept 2021, 20:17 last edited by
Oh sorry!
What I meant is that when trying to build any of the examples, Qt can't find any Vulkan symbols.
It seems it can't find vulkan.h, but isn't generating any explicit errors due to:// In qvulkaninstance.h: #if !defined(Q_CLANG_QDOC) && __has_include(<vulkan/vulkan.h>) #include <vulkan/vulkan.h> #else ... #endif
-
Are you building from Qt Creator ?
-
wrote on 1 Sept 2021, 21:12 last edited by
Yes, I am building from Qt Creator.
-
Did you check that
@John-Doe-2 said in Qt5 Vulkan:
VULKAN_SDK
Is defined in the Build part of the Project panel ?
-
wrote on 2 Sept 2021, 22:27 last edited by
I can see both VULKAN_SDK and VK_SDK_PATH in Build Environment. They are both set to correct values (
C:\VulkanSDK\1.2.182.0
). -
Then I would add something like
INCLUDEPATH += $VULKAN_SDK/includes LIBS += $VULKAN_SDK/lib
to the .pro file.
-
wrote on 3 Oct 2021, 16:21 last edited by
First, excuse me for the late reply. A couple of things came up and I forgot to look into this problem until now.
Second, I reinstalled both Qt and Vulkan and it works now. I think what was happening is that I had improperly installed the Vulkan SDK, but I wasn't having any issues due to it until I tried to use it with Qt.
Thank you very much for your help, and sorry again for the delay.