diff options
| author | Andreas Eliasson <andreas.eliasson@qt.io> | 2023-08-30 14:14:22 +0200 |
|---|---|---|
| committer | Andreas Eliasson <andreas.eliasson@qt.io> | 2023-09-05 23:14:59 +0200 |
| commit | 1e6367e65cb6d00f00d0befa2bf80463b7495e60 (patch) | |
| tree | 596c176774d70635703cc42229ee1c8a01df9fa4 | |
| parent | ebd87ce2e5c1bafd9ae66411a34c9492f1b54be4 (diff) | |
Doc: Add notes that QVulkanFunctions supports Vulkan 1.3
QVulkanFunctions and QVulkanDeviceFunctions now also support Vulkan 1.3.
Fixes: QTBUG-116465
Change-Id: I74f6188330dec1b776b4c6db423b9152ea71d1c3
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
| -rw-r--r-- | src/gui/vulkan/qvulkanfunctions.cpp | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/src/gui/vulkan/qvulkanfunctions.cpp b/src/gui/vulkan/qvulkanfunctions.cpp index e6bf10068ff..6a30799502b 100644 --- a/src/gui/vulkan/qvulkanfunctions.cpp +++ b/src/gui/vulkan/qvulkanfunctions.cpp @@ -13,7 +13,7 @@ QT_BEGIN_NAMESPACE \wrapper \brief The QVulkanFunctions class provides cross-platform access to the - instance level core Vulkan 1.2 API. + instance level core Vulkan 1.3 API. Qt and Qt applications do not link to any Vulkan libraries by default. Instead, all functions are resolved dynamically at run time. Each @@ -45,17 +45,17 @@ QT_BEGIN_NAMESPACE \l{https://www.khronos.org/registry/vulkan/specs/1.0/man/html/vkGetInstanceProcAddr.html}{the man page for vkGetInstanceProcAddr} for more information. - \note The member function prototypes for Vulkan 1.1 and 1.2 commands are - ifdefed with the appropriate \c{VK_VERSION_1_x} that is defined by the - Vulkan headers. Therefore these functions will only be callable by an + \note The member function prototypes for Vulkan 1.1, 1.2, and 1.3 commands + are \c ifdefed with the appropriate \c{VK_VERSION_1_x} that is defined by + the Vulkan headers. As such, these functions will only be callable by an application when the system's (on which the application is built) Vulkan - header is new enough and it contains 1.1 and 1.2 Vulkan API definitions. - When building Qt from source, this has an additional consequence: the - Vulkan headers on the build environment must also be 1.1 and 1.2 capable in - order to get a Qt build that supports resolving the 1.1 and 1.2 API - commands. If either of these conditions is not met, applications will only - be able to call the Vulkan 1.0 commands through QVulkanFunctions and - QVulkanDeviceFunctions. + header is new enough and it contains 1.1, 1.2, or 1.3 Vulkan API + definitions. When building Qt from source, this has an additional + consequence: the Vulkan headers on the build environment must also be 1.1, + 1.2, and 1.3 compatible to get a Qt build that supports resolving + the 1.1, 1.2, and 1.3 API commands. If neither of these conditions is met, + applications will only be able to call the Vulkan 1.0 commands through + QVulkanFunctions and QVulkanDeviceFunctions. \sa QVulkanInstance, QVulkanDeviceFunctions, QWindow::setVulkanInstance(), QWindow::setSurfaceType() */ @@ -68,7 +68,7 @@ QT_BEGIN_NAMESPACE \wrapper \brief The QVulkanDeviceFunctions class provides cross-platform access to - the device level core Vulkan 1.2 API. + the device level core Vulkan 1.3 API. Qt and Qt applications do not link to any Vulkan libraries by default. Instead, all functions are resolved dynamically at run time. Each |