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
Improve MSVC support #584
Comments
This will be handled by #633 |
is this still relevant? |
That is still relevant. However, another item to consider is vcpkg support. vcpkg support should enable users to build a project using libextism on all systems with the same cmake file. There are two goals I'd like to accomplish:
Goal 1 is more important than goal 2, but both are important. I trust your judgement on what next to proceed on. I have revised this ticket with items I believe related to goals 1 and 2. Please let me know if you think we should go in a different direction to accomplish those goals. Info on vcpkg: |
Seems like vcpkg doesn't support rust libraries yet, and I couldn't find a workaround:
But, there is some hope: We can revisit it later on after Rust support is added |
Thanks for looking into vcpkg. Definitely something to watch, but it sounds like it doesn't have the functionality we need yet. |
The MSVC releases do not include an import library (
.lib
) forextism.dll
, only the static library.lib
. The import library makes it possible to "link" to a DLL at build time instead of needing toLoadLibrary
andGetProcAddress
to use extism functions.The libextism cmake file hasn't been tested on MSVC and probably should specify the needed dependencies to link the static version.
.lib
to releasesRelated to #141
The text was updated successfully, but these errors were encountered: