| LICENSE.txt |
|
11473 |
- |
| licenseheader.h.in |
|
144 |
- |
| qbasicvulkanplatforminstance.cpp |
!
\class QBasicPlatformVulkanInstance
\brief A generic platform Vulkan instance implementation.
\since 5.10
\internal
\ingroup qpa
Implements QPlatformVulkanInstance, serving as a base for platform-specific
implementations. The library loading and any WSI-specifics are excluded.
Subclasses are expected to call init() from their constructor and
initInstance() from their createOrAdoptInstance() implementation.
|
19639 |
- |
| qbasicvulkanplatforminstance_p.h |
|
3351 |
- |
| qplatformvulkaninstance.cpp |
!
\class QPlatformVulkanInstance
\since 5.10
\internal
\preliminary
\ingroup qpa
\brief The QPlatformVulkanInstance class provides an abstraction for Vulkan instances.
The platform Vulkan instance is responsible for loading a Vulkan library,
resolving the basic entry points for creating instances, providing support
for creating new or adopting existing VkInstances, and abstracting some
WSI-specifics like checking if a given queue family can be used to present
using a given window.
\note platform plugins will typically subclass not this class, but rather
QBasicVulkanPlatformInstance.
\note Vulkan instance creation is split into two phases: a new
QPlatformVulkanInstance is expected to load the Vulkan library and do basic
initialization, after which the supported layers and extensions can be
queried. Everything else is deferred into createOrAdoptInstance().
|
2082 |
- |
| qplatformvulkaninstance.h |
The following include file did not exist for clang-qdoc running
in macOS, but the classes are documented in qvulkanfunctions.cpp.
clang-qdoc must parse the class declarations in an include file,
or else it can't find a place to put the documentation for the
classes. Apparently these classes are created at build time if
Vulkan is present.
|
3502 |
- |
| qt_attribution.json |
|
801 |
- |
| qvulkandefaultinstance.cpp |
|
3440 |
- |
| qvulkandefaultinstance_p.h |
|
1152 |
- |
| qvulkanfunctions.cpp |
!
\class QVulkanFunctions
\since 5.10
\ingroup painting-3D
\inmodule QtGui
\wrapper
\brief The QVulkanFunctions class provides cross-platform access to the
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
QVulkanInstance provides a QVulkanFunctions object retrievable via
QVulkanInstance::functions(). This does not contain device level functions
in order to avoid the potential overhead of an internal dispatching.
Instead, functions that rely on a device, or a dispatchable child object of
a device, are exposed via QVulkanDeviceFunctions and
QVulkanInstance::deviceFunctions(). QVulkanFunctions and
QVulkanDeviceFunctions together provides access to the full core Vulkan
API, excluding any extensions.
\note QVulkanFunctions instances cannot be constructed directly.
The typical usage is the following:
\snippet code/src_gui_vulkan_qvulkanfunctions.cpp 0
\note Windowing system interface (WSI) specifics and extensions are
excluded. This class only covers core Vulkan commands, with the exception
of instance creation, destruction, and function resolving, since such
functionality is covered by QVulkanInstance itself.
To access additional functions, applications can use
QVulkanInstance::getInstanceProcAddr() and vkGetDeviceProcAddr().
Applications can also decide to link to a Vulkan library directly, as
platforms with an appropriate loader will typically export function symbols
for the core commands. See
\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, 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, 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.
\section1 Security Considerations
QVulkanFunctions is a thin dispatch layer that exposes the Vulkan API as-is.
The arguments are forwarded verbatim to the underlying Vulkan
implementation, which is a trusted, in-process platform dependency. Qt does
not inspect, validate, or sanitize the handles, structures, and pointers
passed in, and does not act on the results returned. Calling a member
function here is therefore equivalent to calling the corresponding Vulkan
command directly, and the valid usage rules in the
\l{https://www.khronos.org/registry/vulkan/}{Vulkan specification} apply
unchanged. Violating them leads to undefined behavior in the Vulkan
implementation, not to a graceful failure from Qt.
\warning All data passed through QVulkanFunctions is expected to be trusted
content. Application developers are advised to carefully consider the
potential implications before deriving any of it from user-provided content
that is not part of the application and is not under the developers'
control. See \l{QVulkanInstance#Security Considerations}{QVulkanInstance}
for more information.
\sa QVulkanInstance, QVulkanDeviceFunctions, QWindow::setVulkanInstance(), QWindow::setSurfaceType()
|
7878 |
- |
| qvulkaninstance.cpp |
|
36067 |
- |
| qvulkaninstance.h |
|
7321 |
- |
| qvulkaninstance_p.h |
|
1862 |
- |
| qvulkanwindow.cpp |
|
110284 |
- |
| qvulkanwindow.h |
|
4660 |
- |
| qvulkanwindow_p.h |
|
5554 |
- |
| vk.xml |
|
2781353 |
- |