-
Notifications
You must be signed in to change notification settings - Fork 4
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
Compilation issues with goexiv library #9
Comments
I had to downgrade to libexiv 0.27 |
I think this would be a good place for us to look for starters: https://github.com/Exiv2/exiv2/blob/v0.28.0/doc/ChangeLog I'm not a big c++ programmer so I'm just plodding through the stacktrace but it looks like some stuff like some data structures got changed:
|
Hey, thanks for reporting this. We don't have the need or resources to update right now. And ultimately I'd rather work with a pure go library instead of integrating with exiv2.
Might be worth trying to open an issue there and see what does the author think. |
From what I understand the problem space of EXIF data is pretty complex and there's probably a reason that people don't really go and reinvent that wheel. It's a problem of a bunch of manufacturers releasing stuff with differing standards on how they exactly represent that data from what I understand, which is why we don't really have a working native go lib. From what I understand that one you linked has enough crashing issues that it's a problem in production, so that's why we went with this |
Hello,
With exiv2 0.28.0
I encountered an issue while trying to compile the goexiv library. I am receiving numerous errors related to the helper.cpp file. I'm not familiar with C++, but if the error is not too complex and some guidance can be provided, I am willing to attempt a PR to fix the issue. Below are the errors I am encountering:
Please let me know if you have any suggestions or guidance on how to approach this issue, and if there are any additional details needed.
Thank you!
The text was updated successfully, but these errors were encountered: