-
Notifications
You must be signed in to change notification settings - Fork 229
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
Even debug builds try to link MSVCRT MT_StaticRelease of SKIA #179
Comments
I'm not familiar with MSVC, but I will look it up tomorrow. Static linking in C/C++ is a nightmare, so I always use dynamic. |
I've had this problem also. My understanding is that Rust uses the Windows release CRT by default when linking, so any calls from the CAPI into Skia.dll fail unless Skia is likewise built for the release CRT (either static or dynamic). There's been some discussion and an open issue on this recently: I hope it gets fixed soon. |
@JaFenix Thanks for clarification. |
Closing as out of scope. |
I'm not sure if this is an issue with RESVG or not.
I need to build a debug build static lib of resvg that links the MT_StaticDebug version of the MSVCRT. This works with the cairo backend, but fails with the skia backend. It seems that that the skia backend always wants to link the static release version, even if i don't call cargo with --release, and then there are errors because skia.lib is linked with the MT_StaticDebug MSVCRT.
here is my build script
and this is the linker error i get
The text was updated successfully, but these errors were encountered: