Skip to content
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

Request: Linux support #150

Open
Adash-nitro opened this issue Dec 19, 2024 · 2 comments · May be fixed by #157
Open

Request: Linux support #150

Adash-nitro opened this issue Dec 19, 2024 · 2 comments · May be fixed by #157

Comments

@Adash-nitro
Copy link

I've been trying the past few days to use MuPDF.NET in a dockerized Linux environment without luck.
same story on WSL2 or an arm-based MAC

I learned the hard way that despite the base C MuPDF being fully capable of running on Linux (even ARM based), MuPDF.NET doesn't support it officially out of the box. There isn't any official information about it either.

Please add it, test it, make it officially support Linux.

This is a huge downside, a deal braker, of this library in a world where everybody on the cloud is shifting fully to Linux or requires the multi-platform nature .NET.

Exception for background:

System.TypeInitializationException: The type initializer for 'mupdf.mupdfPINVOKE' threw an exception.
  ---> System.TypeInitializationException: The type initializer for 'SWIGExceptionHelper' threw an exception.
  ---> System.DllNotFoundException: Unable to load shared library 'mupdfcsharp.dll' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: 
 /app/runtimes/linux-x64/native/mupdfcsharp.dll.so: cannot open shared object file: No such file or directory
 /usr/share/dotnet/shared/Microsoft.NETCore.App/8.0.11/mupdfcsharp.dll.so: cannot open shared object file: No such file or directory
 /app/mupdfcsharp.dll.so: cannot open shared object file: No such file or directory
 /app/runtimes/linux-x64/native/libmupdfcsharp.dll.so: cannot open shared object file: No such file or directory
 /usr/share/dotnet/shared/Microsoft.NETCore.App/8.0.11/libmupdfcsharp.dll.so: cannot open shared object file: No such file or directory
 /app/libmupdfcsharp.dll.so: cannot open shared object file: No such file or directory
 /app/runtimes/linux-x64/native/mupdfcsharp.dll: cannot open shared object file: No such file or directory
 /usr/share/dotnet/shared/Microsoft.NETCore.App/8.0.11/mupdfcsharp.dll: cannot open shared object file: No such file or directory
 /app/mupdfcsharp.dll: cannot open shared object file: No such file or directory
 /app/runtimes/linux-x64/native/libmupdfcsharp.dll: cannot open shared object file: No such file or directory
 /usr/share/dotnet/shared/Microsoft.NETCore.App/8.0.11/libmupdfcsharp.dll: cannot open shared object file: No such file or directory
 /app/libmupdfcsharp.dll: cannot open shared object file: No such file or directory
@jamie-lemon jamie-lemon linked a pull request Jan 14, 2025 that will close this issue
@Adash-nitro
Copy link
Author

Hi, I was tracking the linked PR #157 with high hopes, now I see it's draft and stalled, any updates or some roadmap for this?

@jamie-lemon
Copy link
Contributor

@Adash-nitro Thanks, we are actually still looking at the PR and working out the best approach for the repo for local development as well as being able to publish a cross-platform solution to NuGet. This is why it is in Draft, but in fact we are still looking at it and the best way forward.
In the meantime you can check out the NuGet package from the author of #157 here: https://www.nuget.org/packages/mupdf.net-x64-rn
This is a temporary solution until we have things officially running the way we want with our repo ( and our own internal publishing process to NuGet). Rest assured we will get it done and I hope the temporary NuGet package works for you in the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants