-
Notifications
You must be signed in to change notification settings - Fork 410
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
Provide dynamic framework for cmake / direct clang usage #1328
Comments
Both Are you able to simply link against the static library inside |
It's been a while since I had to dive deep into mac/ios development, but I believe the We changed vulkan-go to look for libraries in the system instead, but that means installing moltenvk is bit more manual. (and distribution would be harder) |
A
Does this mean you no longer need a separate |
For this particular purpose, we found a workaround. See this note. It works, but only for local development. If I wanted to distribute applications using vulkan-go it would require a different approach. Perhaps a better solution is to add make targets to just generate the static/dynamic libraries by themselves without the |
Both the static and dynamic libraries are already available in the package. The static libraries are inside the So...a few options... We could copy the We could also do the same about creating |
Both solutions would cover my concerns. I think just having a documented way to use MolkenVK outside of XCode could be enough. Another option would be simply installing the headers and libraries as any other non-framework library. I.e. copy copy the files to For context: In In the case of Basically, having a defined way to find the libraries would make it easier to maintain the wrapper libraries :) |
It seems the new xcframework type is only supported with xcode. Users wanting to compile with clang need a "normal" framework with dynamic libraries instead.
One solution is to install the dylib in a linker search path, but that only work when there's full control of the compile process.
Libraries like
vulkan-go
are configured to use-F/Library/Frameworks -framework MoltenVK
and there's no good way to adjust the flags without creating a complete fork of the go libraries.Having the option to create a standard MoltenVK.framework would make this much easier!
The text was updated successfully, but these errors were encountered: