https://bugs.kde.org/show_bug.cgi?id=398582
--- Comment #28 from caulier.gil...@gmail.com --- Hi Maik, Some fresh news about my investigations around a Notarization of the digiKam for Windows. - 1/ My plan is to provide a Qt6 based installer - 2/ MXE cannot be used here as QtWebEngine cannot be cross compiled. - 3/ Cross Compiling use Clang-cl toolchain is a pain. See my experimental github repo https://github.com/cgilles/digikam-msvc - 4/ Using vcpkg to cross compile can work for a small project, but vcpkg is not yet designed for that. See my experimental github repo https://github.com/cgilles/digikam-vcpkg-cross - 5/ We needs to use a VM based on Windows 10 + MSVC 2019. See Qt WebEngine spec https://doc.qt.io/qt-6.5/windows-building.html - 6/ We needs a package manager which simplify the job : Craft or vcpkg. I choose vcpkg even if i'm not fan to M$ tool... But i must admit that they do a great job, as all is based to Cmake and it's very simple to use. Also another point about craft : complex configuration and usage, missing package (aka HEIF, AOM, Mysql support), Python based, more dependencies, low support, etc... vcpkg as all in place and is more simple (aka mysql or mariadb, heif, even kf5 !). See the list of portfiles in the project web page https://vcpkg.io/en/ - 7/ I initiate a new github project to compile digiKam under Windows https://github.com/cgilles/digikam-vcpkg-windows. For the moment all Qt6.5.3 compile excepted QtWebEngine, but i found the problem https://github.com/microsoft/vcpkg/issues/34756. All is under recompilation on my lead computer at home https://i.imgur.com/VUjRuma.png - 8/ To notarize the installer there are 2 ways : a self signed, or by an external certification organism (aka for website). First one is for development purpose and can only be used outside the store. This will solve installation process and access rights to the disk, but not the M$ Defender lock at install. This is free but the sign tools from M$ VSCode need to be used under Windows. The second solution is expensive (around 350€ by year) but you can upload to the store and fix all install issues. All are well explained here https://stackoverflow.com/questions/252226/signing-a-windows-exe-file - 9/ To compare, under MacOS, to sign an application you use the Apple tool provided with XCode. The cost is 100 € by year, but it's know that Apple can reimburse the charge for the open source project. I'm in contact with the QtElectrotech team who give me some explanations about https://qelectrotech.org/forum/viewtopic.php?pid=17694#p17694. QtElectrotech uses the digiKam scripts to bundle the applications under Windows (MXE), Macos (Macports), and Linux (AppImage). Voilà Gilles -- You are receiving this mail because: You are watching all bug changes.
