ash
ash copied to clipboard
Consider adding extension dependencies, required version, etc
Hi, would ash consider adding extension metadata to the generated output? In addition to name, I'm referring to the following fields in vk.xml's <extension> tag:
requiresCore: the API version the extension requirespromotedto: the API version in which this extension was promoted to coreobsoletedby: the extension that this extension is obsoleted bydeprecatedby: the extension that this extension is deprecated byrequires: a list of extensions this depends ontype: whether the extension is a "device" or "instance" extension
This would make it much simpler to write device creation code that is parameterized on a dynamic list of required features/extensions.
Here's an example of VK_KHR_get_physical_device_properties2 from vk.xml:
<extension
name="VK_KHR_get_physical_device_properties2"
number="60"
type="instance"
author="KHR"
contact="Jeff Bolz @jeffbolznv"
supported="vulkan"
promotedto="VK_VERSION_1_1">
Many thanks for your time!