(I know, it is a pipe dream to have darktable available on mobile through F-droid.) We now have 64 bit rasberry Pi's, and a lot of android is on 64 bit ARMs. Sorry if I am asking a question WAY out of my league, but what will this mean for building darktable for other 64 Bit ARM architectures? I know there was some interest in the past for running these on other ARM, but, even if it could be complied, it was all on 32 bit, and the claim was it would be crazy slow. So someone needs to backport the ARM64 fix to 0.3.2 release, or figure out the whole mess with lensfun missing a release and being incompatible with parameters from older version. I think homebrew has lensfun package working on M1, but it's version 0.3.95, which is buggy, so it's a no go.
In any case I don't think it's a good idea to release a package without lensfun support. I haven't tested performance yet, I wouldn't be surprised if Rosetta-translated version of darktable actually runs faster than native build.Īnd an open question related to #8589 - do we want to have one universal DMG package for both Intel and ARM64 Mac platforms or make 2 separate DMGs (easier)? Merging 2 builds with some script calling lipo probably isn't hard, but from a practical point of view having an universal build robs a user from an option to use Rosetta-translated darktable, in case native build crashes or is just slower. On darktable side only -DBUILD_SSE2_CODEPATHS=OFF cmake option was needed to make build succeed. libavif - no such port in macports, so missing in my Intel build also, just an additional feature, probably not used/wanted by many.
gtk-osx-application-gtk3 - just some GUI integration sugar, not critical, but nice to have.lensfun - even being optional, it's quite essential to have, since it's needed for an iop.Missing are the following optional dependencies, in order of importance: I've managed to compile and start darktable on M1.
0 kommentar(er)
