-
Notifications
You must be signed in to change notification settings - Fork 220
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 C library in Windows #658
Comments
Here are the Win libraries
I do plan to write build instructions eventually: #564 But I'm not using Windows, so I'm not sure what happens in your case. I would assume you have to link Win libraries (for some reason) required by Rust std, because |
Steps to build resvg C library:
Steps to reproduce issue:
|
You have to link those libs to your executable, not to Rust/ You might want to ask about it in Rust/Cargo repos. This is not a resvg issue, but rather the way Rust builds C libraries on Windows. I don't think there is anything I can do on my side. At least I'm not aware of it. PS: Passing libs to |
You're 100% right. Fixed it by linking the Windows system libraries in CMake. Closing the issue. |
I've been using the C API on Mac and Linux without issues but when I try to link on Windows I get "unresolved symbol" errors that seem to refer to Windows system libraries. With
rustup==1.72.0
I get 32 errors, while withrustup==1.69.0
I get 29 errors, so maybe the problem lies on their end. I am making sure to set the RUSTFLAGS env variable following a previous issue.Meanwhile I can build and run
resvg.exe
on Windows without any problems. Perplexing!I setup a simple test repo here: https://github.com/makarr/resvg_lib_test
Even if the fault does not lie with
resvg
I would be thrilled if someone could explain how to get the C API to work on Windows.The text was updated successfully, but these errors were encountered: