Hi @guzzisti, thanks for your efforts. Do you plan to put your PKGBUILD on the AUR?
I compared the results with Rawtherapee’s manual compilation method (with Morgan Hardwood’s script)…
I guess i should do so. 
Having ART in the AUR would be the logical next step. Unfortunately i have never messed with the AUR as a contributor. I guess some additional steps need to be taken before submitting the PKGBUILDs.
I will have a look at this the next days. Any help, especially testing and package review or advise by an experienced AUR packager is greatly appreciated. I’ll track progress in this issue.
As there are the same build optimization applied on both, there should be no difference in performance.
1 Like
MSYS2/windows10
- I had to downgrade the mingw64package:
$ pacman -U /c/msys64/var/cache/pacman/pkg/mingw-w64-x86_64-cmake-3.15.6-1-any.pkg.tar.xz chargement des paquets… avertissement : retourne à la version antérieure du paquet mingw-w64-x86_64-cmake (3.16.4-1 => 3.15.6-1)
mingw-w64-x86_64-cmake-3.16.4-1 crashes on a segmentation fault.
- Is there somebody that ever succeded to build with LTO option on MSYS2? is it worth the effort? How did you proceed exactly ( compiler, linker, options…) ? Are there some problems in the source that can preclude use of LTO?
AFAIK I am using the official MSYS2 repository. Here is link to the pacman configuration I am using to install the MSYS2 packages:
https://raw.githubusercontent.com/aferrero2707/docker-buildenv-mingw/master/pacman-msys.conf
As a check, I took the official package, extracted it an checked the size of the libexiv2.dll library, and I get 2.8 MB:
So this seems to be consistent with what the library that is present in my bundles.
Should I use a different MSYS2 repository?
Thanks!
I think this comes from the RawTherapee packaging, I vaguely remember that the developers suggested to include it…
1 Like
I am really puzzled 
You use the same repo as the same official package repo, you use the last version, the size in official repo is as you say!
So I surely did something but what! I have to search.
I had a discussion with @agriggio on this subject. Perhaps he remembers.
@Carmelo_DrRaw, the official exiv2 version in Mingw seems broken, or at least miscompiled. it seems it doesn’t properly raise exceptions on error. if I compile it myself, everything works. I think @gaaned92 does the same now after we talked about this.
Thanks @agriggio. With age we loose memory 
edit : I was only able to build the tag 27.2. It failed on last master and on 27.2-maintenance.
@Carmelo_DrRaw: I can send you the good dll if you can copy it in the build.
Can you elaborate at bit more on what you are doing?
I just placed the css into the base folder /usr/share/ART/themes/ and blackfoxx appears in the preferences dialog - but i’m not sure if that is the right way to add a theme to ART/RT.
Yes, that’s right. I did that, too, but it doesn’t show up in the preferences dialog and i don’t know why…!??
what’s your gtk version?
To know the exact version, check the gtk3 package version in the package manager.
Actually i have no clue whats going wrong, despite using a newer kernel and Cinnamon my Manjaro install should be pretty much the same.
Could you try the updated PKGBUILD? Please uninstall the previous package first.
I prefer to add the compilation of EXIV2 from sources in my build scripts, so that they remain self-consistent.
Should one also compile exiftool from sources?
no, that’s not necessary (it is a perl script btw, just wrapped in a standalone .exe for Windows)
No need to mess around with the theming anymore 
i had a short chat with @blackfoxx and he agreed to integrate the theme into the package.
The updated PKGBUILD files now automagically integrate the theme into the package.
1 Like
Yeeeaaahh!!! 