Using wayland:client for wayland bindings. #10
Conversation
wayland-client-d is not maintained anymore. [wayland:client](https://github.com/rtbo/wayland-d) replaces it.
|
I am really sorry for the delayed reply. Thanks for Information and pull request. I have no linux test system so I need to trust you on this, but I noticed one thing: |
|
|
||
| enum VK_KHR_WAYLAND_SURFACE_SPEC_VERSION = 6; | ||
| enum VK_KHR_WAYLAND_SURFACE_EXTENSION_NAME = "VK_KHR_wayland_surface"; | ||
|
|
||
| alias VkWaylandSurfaceCreateFlagsKHR = VkFlags; | ||
| struct wl_display; | ||
| struct wl_surface; | ||
| alias wl_surface = wl_proxy; |
There was a problem hiding this comment.
VkWaylandSurfaceCreateInfoKHR has a field of type wl_display* but you have removed the definition of that type, how can this work?
There was a problem hiding this comment.
wl_display is imported by wayland.native.client.
Having a local definition makes erupted expecting erupted.types.wl_display, whereas application code is supplying wayland.native.client.wl_display
There was a problem hiding this comment.
Sorry for the late reply. I have no opportunity to test this, but I assume that it works at your side, hence I will trust you.
Btw, I don't like the fact that erupted has so many dependencies even if not used. I am working on (or rather postponing ...) a version which does have no dependencies at all, and all the platform specific code is implemented as several template mixins. So its in the users hand to decide which libraries he wants to use. What do you think about this approach?
|
Btw, how impolite of me! Thanks for the note and contribution! |
wayland-client-d is not maintained anymore.
wayland:client replaces it.