summaryrefslogtreecommitdiffstats
path: root/src/gui/doc/snippets/textdocument-blocks
diff options
context:
space:
mode:
authorLaszlo Agocs <laszlo.agocs@qt.io>2020-02-29 15:38:07 +0100
committerLaszlo Agocs <laszlo.agocs@qt.io>2020-03-03 18:25:57 +0100
commitbd2b77120e1db8cb991aff23dd1f99cec792fa8e (patch)
tree38664e0dc6252dc753605bcc708b0c08c3b5efb0 /src/gui/doc/snippets/textdocument-blocks
parent5bbc9986f99a5d61c2e43b79fe815ea8ca450fcd (diff)
rhi: vulkan: Sanitize device extension handling
Instead of qputenv("QT_VULKAN_DEVICE_EXTENSIONS", "VK_KHR_get_memory_requirements2;VK_NV_ray_tracing"); one can now do params.deviceExtensions = { "VK_KHR_get_memory_requirements2", "VK_NV_ray_tracing" }; on the QRhiVulkanInitParams passed to QRhi::create(). The environment variable stays important for Qt Quick applications, which provide no configurability for the QRhi construction (yet). On the other hand, applications using QRhi directly can now also use the new approach to specify the list of device extensions to enable. In addition, take QVulkanInfoVector<QVulkanExtension> into use. There is no reason not to rely on the infrastructure provided by QVulkanInstance. This also implies showing an informative warning for unsupported extensions, instead of merely failing the device creation. (applications will likely not be able to recover of course, but at least the reason for failing is made obvious this way) Task-number: QTBUG-82435 Change-Id: Ib47fd1a10c02be5ceef2c973e61e896c34f92fa3 Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
Diffstat (limited to 'src/gui/doc/snippets/textdocument-blocks')
0 files changed, 0 insertions, 0 deletions