https://signpath.org/ is asking us to set up a CI/CD pipeline...
It’s already very complicated to compile QET for Windows; setting up a CI/CD pipeline on our GitHub is even more complicated.
For years (15 years) I have been providing QET packages for Windows; they are cross-compiled on my Debian machine using MXE and based on the old scripts from the Digikam developer. See: https://qelectrotech.org/forum/viewtopi … 976#p13976
Cross-compilation is an advantage for me as everything is scripted, but it involves compromises: static builds, EXE files containing the DLLs, and deployment with winqtdeploy not working in cross-compilation!
Furthermore, the NSIS installer scripts are still based on the old 2.X version; I don’t have the time and nor healthor, the skills to rewrite them to make them compatible with NSIS 3.X.
https://qelectrotech.org/forum/viewtopi … 226#p17226
We are therefore looking for people with expertise in Windows CI/CD, as well as people capable of reviewing the Windows installer.
"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !