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
Portability guide for 0.28.0? #2630
Comments
Here's the kfilemetadata5 issue for this: |
geeqie one: BestImageViewer/geeqie#1090 |
Too much breakage: Exiv2/exiv2#2630
too much breakage, wait for fixes for geeqie, gexiv2, kfilemetadata5 Exiv2/exiv2#2630
Use toInt64 instead |
Thanks. Do you have suggestions for geeqie too? |
In 0.28.0, we have attempted to eliminate the |
Btw, this seems to be always true for me (MSYS2 UCRT64 GCC 12.2) now somehow for any type exiv2/include/exiv2/xmp_exiv2.hpp Lines 398 to 402 in 0a9b57a
so e.g. this darktable code now fails:
|
Also had to change |
I have a patch for this. |
After speaking with ChatGPT, it seems if constexpr should be removed from headers. |
That's great! Is it for exiv2 or geeqie? If the latter, can you please share it with at BestImageViewer/geeqie#1090 ? |
Well, looks like Arch maintainers did it: https://archlinux.org/todo/exiv2-028/ 🚀 |
Great |
geeqie is fixed. can this issue be closed? |
Thanks for the help! |
0.28.0 broke a couple of exiv2 users. Please advise how the code should be updated.
kfilemetadata5 (https://github.com/KDE/kfilemetadata/blob/master/src/extractors/exiv2extractor.cpp)
geeqie (https://github.com/BestImageViewer/geeqie/blob/master/src/exiv2.cc)
geeqie.log
gexiv2 (https://gitlab.gnome.org/GNOME/gexiv2/-/issues/74)
gexiv2.log
Thanks!
The text was updated successfully, but these errors were encountered: