-
Notifications
You must be signed in to change notification settings - Fork 32
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
bin2coff exists with code 1, executed with invalid path #72
Comments
I have same problem. When I put I found these fonts files are excluded in [package]
edition = "2018"
name = "mupdf-sys"
version = "0.4.2"
authors = ["messense <[email protected]>"]
links = "mupdf-wrapper"
exclude = [
"mupdf/resources/cmaps/*",
"mupdf/resources/icc/*",
"mupdf/resources/fonts/droid/*",
"mupdf/resources/fonts/han/*",
"mupdf/resources/fonts/noto/*",
"mupdf/resources/fonts/sil/*",
"mupdf/resources/fonts/urw/input/*", |
Unfortunately crates.io has a size limit, so we can't include all of the fonts. For now, you can try to use git dependency instead. |
Hey i have the same issues with the driod sans fallback.ttf - what was the work around in this case?? |
Those experiencing similar issue on Windows machines can try the following suggestion:
where
|
Same problem when compile for |
@messense what is the size limit, why is it impossible to include these fonts in package? |
Ooh, there is other problem. Why building for target x86_64-pc-windows-msvc requires these font files but building for linux or etc does not? I think there is some problem with build defenitions for windows target, but I cannot see it. @messense maybe you can help with it? |
When trying to add the mupdf crate to an empty project and building it on windows, I get the following error:
The mentioned directory for the font
"C:\dev\Rust\mupdf-test\target\debug\build\mupdf-sys-61a5ef3cbd8e3793\out\build\resources\fonts\droid\DroidSansFallback.ttf"
doesn't exists in the build directory.I couldn't find something similar online, so I thought I might ask here.
The text was updated successfully, but these errors were encountered: