https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #21 from caulier.gil...@gmail.com --- For Craft, i tried few years ago to use it without success : Mysql/mariadb support in Qt not supported. I ask to add it but it was immediately refused : this require changes with server included and many dependencies. HEIF support not implemented with X264 and x265 codecs. About patents, this cannot be included safety. ffmpeg do not include non free / gpl3 codecs support. The puzzle: plenty of applications uses craft build with different needs / config / usage. This is not compatible with the digiKam requirements. We needs a stable env to bundle, not soething broken days after days because plenty of developer touch the configurations without to double check all the usage. The CI/CD from KDE uses gitlab, whoch is limited to one hour of compilation. digiKam and 3rd party plugins + build packaging explode this limit. digiKam is 1.5 M od C++ code. If we touch something in core API, all will be recompiled and compilation cannot be completed. For all this problems, i focused to Macports and this take age for me to maintain and finalize packaging. Here i have 2 macbook pro : one intel and one Arm. I written ann bash scripts to package all digiKam needs, as Mysql support, codecs, relocatable install, etc. Of course installer is not notarized, but we don't care... It's always possible to install digiKam as 3r party application outside the store. Note: the same problematic exists with the Windows build. We don't use Craft but VCPKG from Microsoft and it do very well the job. Here 2 Windows 10 VMs run on my Linux host computer : one for Qt5, one for Qt6. Voilà, so for me Craft is not a safe solution for digiKam... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
