-
Notifications
You must be signed in to change notification settings - Fork 43
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
Can't compile with msvc, "cannot open input file 'freetype.lib'" #65
Comments
Hi @mrZalli! The error you get is saying that the MSVC linker can't find the freetype lib file. If it is, your config might not get loaded by cargo or you specified a wrong target. Check out the "overriding build scripts" section in the cargo documentation. |
Thanks for the response, though at the time when I tried to build that I was probably using MinGW, so link.exe is not MSVC linker, but MinGW linker. I've now moved to using MSVC on Windows, and I think I should try doing this again and see if the problem persists. |
You were already using MSVC, the MinGW linker isn't called "link.exe" and the path shown by cargo is |
Oh okay didn't notice that path. However when when I typed "where link" in cmd, it pointed to a link.exe in MinGW folders |
I am also using MSVC. How can I configure so that I can load freetype.lib? |
A different solution would be to use freetype instead of freetype-sys or freetype-rs, because that builds the whole freetype C code when compiling and includes the necessary Rust bindings. The API is more or less the same, but the code is statically linked instead of dynamically. This way it'll work on all platforms, regardless of OS and you don't have to ship a freetype.dll to customers, so it's all in one binary. |
Hi, I've been trying to compile the Kiss3D example program but I can't get past linking the freetype library. I did the config file as suggested in readme and I tried both .lib and .dll binaries, but both give the same error message on the linking stage, " cannot open input file 'freetype.lib' "
Here is the error log (using .dll binaries):
The text was updated successfully, but these errors were encountered: