I would be very convinient if Qt was pre-installed in the Windows environment, since it’s takes some effort and time to install without a GUI. AppVeyor does this and it works very well.
Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.
Good to hear, thanks!
Not sure why this was moved to “How to use Git and GitHub” though, it’s specifically about GitHub Actions.
In the meantime, does anyone have a recipe for installing Qt in Github’s Windows CI environment?
This almost works (requires this script available on the CI machine):
steps: - uses: actions/checkout@master - name: install Qt run: | @echo on @prompt $G$S @echo --- Qt install cmd script %~dpnx0 pushd %GITHUB_WORKSPACE% pushd tools curl -vLo qt-unified-windows-x86-online.exe http://download.qt.io/official_releases/online_installers/qt-unified-windows-x86-online.exe qt-unified-windows-x86-online.exe --verbose --script qt-installer-windows.qs
Unfortunately there’s still a problem:
 Created warning message box “installationErrorWithRetry”: “Installer Error”, “Error during installation process (qt.tools.vcredist_64):\nExecution failed (Unexpected exit code: 1603): “C:\Qt\vcredist\vcredist_sp1_x64.exe /norestart /q””
This SO question Qt SDK installation errors on Windows 7 indicates we might be able to slap [ignore] and keep going. I don’t know how to add to the script though.
I am using
Download entire Qt with debug symbols every time build triggers? Github really don’t care about bandwidth wasted on build environments that can be nicely cached?
There is an action to make it even easier: https://github.com/jurplel/install-qt-action