-
Notifications
You must be signed in to change notification settings - Fork 3
Updating Qt
Ingrater edited this page Oct 16, 2022
·
2 revisions
- Follow the instructions here to clone the Qt repository and install the prerequisites (perl, ruby, ninja, cmake): https://wiki.qt.io/Building_Qt_6_from_Git
- The following examples will assume you cloned to
C:\code\qt
- Create a folder for building:
C:\code\qt\qt6-build
- Create a folder for the final output:
C:\code\qt\install
- Start a
x64 Native Tools Command Prompt for VS 2022
. Make sure it has both ruby and perl in thePATH
. - cd into
C:\code\qt\qt6-build
- Run the qt configure command:
..\configure.bat -submodules qtsvg,qtbase -nomake examples -nomake tests -prefix C:\code\qt\install -debug-and-release -force-debug-info
- Build:
ninja
- Produce the final package:
ninja install
- Now rename the
install
folder to your new Qt version. e.g.Qt6-6.4.0-vs143-x64
. Zip the resulting folder using 7z so that the 7z file contains theQt6-6.4.0-vs143-x64
folder.
- Create a new tag in the https://github.com/ezEngine/thirdparty repository. Give it the same name as the new qt version e.g.
Qt6-6.4.0-vs143-x64
- Create a new release from this tag and attach the 7z file you created earlier.
- Change the path in the
ezCMakeConfig.cmake
in the ezEngine main repository to point to this newly released 7z file.
- On our azure account download the current thirdparty zip from the
ez-container
container. Remove the old QT version, and add the new one. - Crate a new thirdparty zip and upload it to
ez-container
- Create a SAS for the new thirdparty zip and give it a end date far in the future
- Now update the secret
ThirdPartyWinx64Qt6
in ezKeys and store the new SAS url there. Alternatively you can also create a new secret and change theCode\BuildSystem\AzurePipelines\Windows-x64.yml
pipeline to access the new secret instead.