ic/magnum - magnum - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Vladimír Vondruš	63acbc7a22	Vk: it's inevitable, DeviceProperties are going to stay forever. I have more and more cases where I need to query device properties later down the road (memory capabilities, device name, ...) and leaving all this up to the user / making this impossible to do in the library internals is complicating everything too much. Since there's a shitton of device properties with a new bag of props coming with every other new extension, I expect the queries to get quite involved / complicated over time (chaining 100s structs and such), so let's design this upfront in a way that can avoid reqpeatedly querying the same thing just because we needlessly discarded a fully populated instance before. It also means the users don't need to drag their own DeviceProperties instance along anymore and can just let the Device take care of that. Unfortunately the only nice way to make this work with DeviceCreateInfo method chaining is to add & and && overloads for each. But it's quite easy to test that all of them work and properly return a r-value reference so it shouldn't be too much of a maintenance nightmare.	6 years ago
Vladimír Vondruš	791d3d44e9	Vk: implicitly enable VK_KHR_bind_memory2 on Vulkan 1.0.	6 years ago
Vladimír Vondruš	14dbc43fce	Vk: implicitly enable VK_KHR_get_memory_requirements2 on Vulkan 1.0.	6 years ago
Vladimír Vondruš	c6f377b45f	Vk: this DeviceCreateInfo constructor is garbage. It only adds confusion and can be replaced by only a moderately longer but infinitely more descriptive oneliner. Delete.	6 years ago
Vladimír Vondruš	55ec24062d	Vk: GCC 4.8, stop it, it's not Monday today.	6 years ago
Vladimír Vondruš	f75cc9330c	Vk: a non-error-prone way to retrieve queues after device creation. I wonder why this couldn't be done this way in the Vulkan API directly.	6 years ago
Vladimír Vondruš	374f816762	Vk: device creation.	6 years ago