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

Linking with Vulkan Memory Allocator #804

Open
dylanede opened this issue May 18, 2023 · 1 comment · May be fixed by #805
Open

Linking with Vulkan Memory Allocator #804

dylanede opened this issue May 18, 2023 · 1 comment · May be fixed by #805

Comments

@dylanede
Copy link

dylanede commented May 18, 2023

I have previously successfully used skia-safe in conjunction with ash and vk-mem-rs to build a Vulkan-based 3D application with an overlay rendered with Skia. This was with version 0.47.0 of skia-safe.

I have now started on another application with a similar setup, using the latest version of skia-safe - 0.62.0. Unfortunately with this version I encounter duplicate symbol errors for the symbols from Vulkan Memory Allocator (VMA). VMA is used internally in Skia, which is conflicting with my use via vk-mem-rs (Rust bindings for VMA). Since Skia does not expose VMA's API publicly, is there any way to hide these symbols so that they do not conflict with those linked by vk-mem-rs?

I am not yet sure what was different in the earlier version of skia-safe that allowed linking to succeed, since that version still depended on VMA. Note that I am using the same version of vk-mem-rs as before.

Note that all of the above is with MSVC x86_64 on Windows 10. I have not yet tested whether this works on other platforms.

@dylanede
Copy link
Author

dylanede commented May 18, 2023

Indeed, I have just tried switching to version 0.47.0 from 0.62.0 on my current project, and that links successfully. I will try to find the version that introduces the problem.

Edit: It appears to be between 0.50.0 and 0.52.0.

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

Successfully merging a pull request may close this issue.

1 participant