[WIP] Cura 8640 PyQt6 upgrade

[jellespijker]

In order to get this to work on our build-system and working for all three OSes we did a shit tons of boy scouting in our cmake. We removed old methods with variables and try to be consisted in a target-based approach. The idea is that we don't patch stuff down the line, but that the install should place everything with desired rpaths for each project.

Most of the changes had to do with how dependency targets were named and to make sure that external projects weren't downloaded automatically.

Part of

• ultimaker/libarcus#134
• ultimaker/pynest2d#17
• ultimaker/libsavitar#41
• ultimaker/libnest2d#3
• ultimaker/cura-binary-data#17
• ultimaker/libcharon#40
• ultimaker/curaengine#1639
• ultimaker/uranium#804
• ultimaker/cura#11792
• ultimaker/cura-build#280
• ultimaker/cura-rundeck-jobs#1

Fixes

• 79 We now use the System based Python

• 122 We use 3.10.4 now as base

• 114 No longer build in Docker on Windows

• 110 No longer build in Docker on Windows

• 111 We no longer use Jenkins

• 122

• 97 Yeah

• 95

• 90 Compiling with MSVC Visual Studio 2019 and 2022 works, WSL and/or Docker on Windows are no longer supported

• 89 Docker on Windows no longer supported. We are currently building in a Windows VM using the x64 MSVC Visual Studio 2019 or 2022

• 81

• 78

Todo

• [x] Update Readme. But maybe best done in a separate ticket to prioritize with our other work for the 5.0 release. See #121 and CURA-9047
• [x] Make sure the additional VC redist files are installed as described in ultimaker/cura-binary-data#17
• [x] Check and fix if confirmed CURA-9105 Uninstall Cura.exe doesn't uninstall the program
• [x] Check and fix if confirmed CURA-9103 Order of files in installation folder scrambled
• [x] Clean up and remove setting the branches and versioning in the conanfile.py
• [x] Remove Windows Docker files since we now build directly on a VM with Visual Studio 2019 and/or Visual Studio 2020 compiler.
• [x] Remove old environment scripts
• [x] Remove Jenkinsfile
• [x] Create a cmake target which allows the installation of a virtual environment (excluding Cura, Uranium and CuraEngine)
• [x] Create installer for MSI. Might be best to do this in a seperate ticket after the 5.0 release

[jellespijker]

Thanks @Ghostkeeper

TLDR; I'm reluctant to implement your bigger changes. Certainly given the time constraints we are already facing. I will change the smaller comments and I think @evtrados should implement the build version number on the Rundeck side

Yes you're correct with regards in the Dockerfile. These are based on the Conan Docker tools and could be simplified for our purpose. Something which I would certainly do if this repo still has a long life in front of it. But because we're switching to a new build setup with Conan as dependency manager and pipelines to build the dependencies and store them on an artifact server. All artifacts will be build on VM's instead of using a Docker Image.

The same goes with the readme We should probably update this, certainly after the beta release. But it will be very minimal. Basically stating that CMake needs to be called with: CMAKE_PREFIX_PATH and CMAKE_INSTALL_PREFIX since that will be basically what we do on the build servers as well. Okay I will also state the minimum requirements: CMake, Conan, Python, GCC, Apple-Clang or MSVC but no elaborate docs.

I see value in the build version remark for our current build system, but I do think that this should be handled on the Rundeck side, such that all three OS build jobs will get the same timestamp as build version. I'm hoping @evtrados can pick this up

[jellespijker]

Created a ticket CURA-9157 for the MSI installer

[jellespijker]

Removing the CMake variables for the branches is best done by @evtrados when he creates the Rundeck scripts

[jellespijker]

See CURA-9105 for the uninstaller

[jellespijker]

I have updated the readme with the minimal information.

I have left out the Docker use case Since that is basically just a tool for us, to have a reproducible environment.