On Mon Aug 3 08:29:08 2026 +0000, Elizabeth Figura wrote:
I was halfway through trying to convert things to use the host vkCreateImage when I realized it doesn't actually make things any more future-proof. The problem is that in the case of a dedicated allocation we need to unwrap the image, but currently that's a no-op. So either way there's a no-op conversion between PE and Unix VkImage that risks getting missed. Yeah, and it seems brittle to me, if we end up needing a VkImage wrapper we might miss this. It seems cleaner to me to have unix-created objects be used on the unix side only, while PE-side created object might be used across sides more freely.
Also, as you say we might want to skip the blit later on, and share the resource directly, it seems to me that there's a lot of synchronization aspects that simply will require a proper shared resource, so IMO might be better to investigate that way already. Then this MR doesn't require any change in win32u, so if you feel this is good enough for now I don't really mind. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11535#note_147630