-
Notifications
You must be signed in to change notification settings - Fork 168
Adding libheif support breaks build #23
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
Comments
I'm not an expert in libheif so not sure if this will help, but to me this looks like you're using a version of libheif that is not compatible with that particular standard library. to me it seems that it's not complaining about a missing library, but that the library it links to does not have |
I will try this out later, but this was just one of the many errors. A lot of them included missing references to |
try building imagemagick using https://github.com/lambci/yumda instead - that uses RPM packages for that specific version of Linux, so it is likely to work smoother |
I gave it another shot, turns out I forgot to add the quotes around the |
It would be nice if @ericdevries' additions were merged into the mainline. Really helpful! |
I noticed somebody else forked my version, so I made a pull request on this repo so that the fragmentation of implementations can be reduced |
I forked your repo with HEIF support. Would be great to get it into this repo to keep things clean! |
I tried adding HEIF/HEIC support to the build process, the library itself builds fine but when you start building the imagemagick binaries it complains about not having any references to basic c++ libraries. See a sample below.
I am no expert on this matter, but when building this stuff in a different environment it just seems to work, so I wonder if there could be given any pointers on how to make it build correctly with libheif support built in?
Some output from the build process:
My additions to the Makefile_Imagemagick file:
The text was updated successfully, but these errors were encountered: