Using VMA version 3.3.0

This is a ziggyfied wrapper over VulkanMemoryAllocator that also exposes the C API.

• Add the repo to your build.zig.zon file with:

zig fetch --save git+https://github.com/MakeItEnd/zig_vma#main

• Add this to your build.zig:

const zig_vma_dep = b.dependency("zig_vma", .{
    .target = target,
    .optimize = optimize,
});
const zig_vma = zig_vma_dep.module("zig_vma");

// IMPORTANT: Add vulkan-zig import to zig_vma!
// --- vulkan-zig
const vulkan = b.dependency("vulkan", .{
    .registry = b.dependency("vulkan_headers", .{}).path("registry/vk.xml"),
}).module("vulkan-zig");
// --- vulkan-zig

zig_vma.addImport("vulkan", vulkan);

// ...

exe.root_module.addImport("zig_vma", zig_vma);

Most wrapped methods for equivalent C functions that would return vk.Result will convert that to a zig error if typically only one variant of it is returned and its a clear error. It keeps the return type when multiple variants of vk.Result are returned that each denote a specific problem with the users vulkan code, or the VMA documentation doesn't specify the variants.

For the VulkanMemoryAllocator wrapper all C functions were renamed to:

For the VirtualBlock wrapper all C functions were renamed to:

With the exception of the Allocator and VirtualBlock handles all other handels and struct are re-exported from the c namespace into root for ease of access.

The c namespace is mostly useful only if you want to call the C functions directly.

• Finish C API.
• Write a wrapper over the functionality.
• Add example.
• Improve documentation.
• Convert more vk.Result returns form wrapped functions to a more zig-like response.