Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving from gfx-hal to ash #1

Open
tsahyt opened this issue Feb 7, 2023 · 0 comments
Open

Moving from gfx-hal to ash #1

tsahyt opened this issue Feb 7, 2023 · 0 comments

Comments

@tsahyt
Copy link
Owner

tsahyt commented Feb 7, 2023

Some time ago, gfx-hal was deprecated in favour of wgpu-hal since it only functioned as an abstraction layer to build wgpu on anymore. Unfortunately, for this project this meant that our hardware abstraction layer is stranded. Originally gfx-hal was picked in order to support multiple graphics APIs across several platforms. I don't deem this as important anymore. Supporting "only" Vulkan should be plenty, and the project was never tested on anything other than Vulkan to begin with.

Moving to ash should provide the lowest friction, since gfx-hal closely mirrored the Vulkan API. In the process it would also be worth looking into moving to a dedicated allocator library, and deprecating our custom allocators.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant