I finished generating C enums, bitsets, function pointers, structs, unions and handle declarations from the Vulkan API registry. I wrote an article on the topic with a link to the current output module [1].
I tried using dynamic-ffi but hit an issue re: header selection that I expect will be resolved [2]. I still intend to include use of it for those who prefer its interface. My intended experience is for (require vulkan/unsafe) to include Vulkan C-types into the module namespace. I'd like to ask anyone interested in this project and with Vulkan/FFI experience to review the output code linked in the article and point out any erroneous patterns. Since I'm learning ffi/unsafe as I go, I expect I've done a few things wrong, or inefficiently. I'd want to know that sooner rather than later. I hope to be test-ready by end of next week. After that comes extension support, and finally porting @Erkaman's Mandelbrot set renderer to implement the first test [3]. ~slg [1]: https://sagegerard.com/racket-vulkan-types-done.html [2]: https://github.com/dbenoit17/dynamic-ffi/issues/27 [3]: https://github.com/Erkaman/vulkan_minimal_compute -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/ZhQGm7uHROBBlq-5Ff7WiItvvS-SeDeqNlwZMWmKWIReDK-9viFg_5RhdHDVGFzJs5QVGexdIRZ-YNhvL5wd0NJrvBo8cR0IjZV6kC-M5_s%3D%40sagegerard.com.
