-
Notifications
You must be signed in to change notification settings - Fork 14
thumbnail auto_rotate option doesn't work since vips isn't built with libexif #4
Comments
Always a joy to hear from you Mike! :) Please do investigate more and let me know what you find. Maybe even make work in progress pull request that I can checkout and toy around with too. |
I've recently re-done the whole Dockerfile (for Ruby 2.7) which means it should be easier to add this if needed. Take a look. |
got that working with the latest docker image, hope that helps
|
Thanks, mind making a PR to the |
I can add a commit for it. Looking at this though:
I'm not quite sure what that's designed to achieve. If the goal is to handle the symbolic link properly then I think this needs to be written differently, because: the |
Also, after reviewing the dependencies, |
Well I went with a complete different solution since I use python 3.7, and I can definitely post the dockerfile here tmr, but at the end we had some issue with this build you are proposing. And I'm not good at devops so was just trying to help here and you know better for sure. |
And we appreciate that!!! |
It's me again :)
I noticed that when compiling vips - its compiled without exif support. Exif support is needed in order for autorotate options when using the thumbnail method.
(libvips/libvips#319)
I tried a few things to no avail and will try again soon to get this working but wanted to put some info here
For sure yum needs to install
libexif-devel
so vips will build with exif supportThen we need to figure out how to referencethe libexif.so files in the layer files somehow. I'm not aware how to do this at this time but I did try symlinking and copying some libexif.so files into share/lib directory without success.
When loading vips the lambda responds with this error:
"errorMessage": "Could not open library 'vips': vips: cannot open shared object file: No such file or directory.\nCould not open library 'libvips.so': libexif.so.12: cannot open shared object file: No such file or directory",
The text was updated successfully, but these errors were encountered: