messense / mupdf-rs

Rust binding to mupdf
GNU Affero General Public License v3.0
96 stars 21 forks source link

bin2coff exists with code 1, executed with invalid path #72

Open swip3798 opened 1 year ago

swip3798 commented 1 year ago

When trying to add the mupdf crate to an empty project and building it on windows, I get the following error:

C:\dev\Rust\mupdf-test\target\debug\build\mupdf-sys-61a5ef3cbd8e3793\out\build\platform\win32\bin2coff.targets(76,5): error MSB3721: The command "Release\bin2coff.exe "C:\dev\Rust\mupdf-test\target\debug\build\mupdf-sys-61a5ef3cbd8e3793\out\build\resources\fonts\droid\DroidSansFallback.ttf" "x64\Release\libresources\DroidSansFallback_ttf.obj" _binary_DroidSansFallback_ttf x64" exited with code 1. [C:\dev\Rust\mupdf-test\target\debug\build\mupdf-sys-61a5ef3cbd8e3793\out\build\platform\win32\libresources.vcxproj]

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.

kusaanko commented 11 months ago

I have same problem. When I put resouces/fonts on https://github.com/ArtifexSoftware/mupdf in mupdf-rs-sys-0.4.2/src, I can compile mupdf-rs.

I found these fonts files are excluded in Cargo.toml of mupdf-rs.

[package]
edition = "2018"
name = "mupdf-sys"
version = "0.4.2"
authors = ["messense <messense@icloud.com>"]
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/*",
messense commented 11 months ago

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.

meanjellybean1 commented 5 months ago

Hey i have the same issues with the driod sans fallback.ttf - what was the work around in this case??