gulkan-device: fix Compile on vulkan without VK_EXT_memory_budget
Is it fine to have these functions be noop at runtime when gulkan is compiled with too old vulkan headers or do we want to try a proper fix?
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Is it fine to have these functions be noop at runtime when gulkan is compiled with too old vulkan headers or do we want to try a proper fix?