Home → Questions →

Qt Installer Framework is not available under Visual Studio 2019 image

• Edit

Mark Ts

12 Mar, 2020 09:08 PM

Right now deploying application that utilizes Qt 5.14 is broken within appveyor.

Visual Studio 2017 hasn't Qt 5.14 and Visual Studio 2019 hasn't Qt IFW. Any reason\estimation when Qt 5.14 will be added to Visual Studio 2017 image and when Qt IFW will be added to Visual Studio 2019 image?

1. Support Staff 1 Posted by Feodor Fitsner on 12 Mar, 2020 09:24 PM

   

   Hi Mark,

   We are in the process of updating images.

   On VS 2019 there is Qt IFW in C:\Qt\Tools\QtInstallerFramework\3.2\bin location. Could you give a try please and let us know how that worked?

   • Edit

2. 2 Posted by Mark Ts on 12 Mar, 2020 10:00 PM

   

   Hi Feodor,

   Thank you for very fast reaction, I appreciate all the help you provided me with.

   Could you give a try please and let us know how that worked? That worked thanks once again for helping!

   and one more question is there any chance that you know a path to Qt vcredist inside VS 2019 image?
   previously it was C:\Qt\vcredist\vcredist_msvc2017_x86.exe\C:\Qt\vcredist\vcredist_msvc2017_x64.exe but now there is no such path

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 12 Mar, 2020 10:04 PM

   

   Is vcredist required for QTIFW to work?

   • Edit

4. 4 Posted by Mark Ts on 12 Mar, 2020 10:11 PM

   

   Is vcredist required for QTIFW to work?

   No it's not, right now the problem with Qt IFW is solved.

   vcredist is just quality of life question, previously I used vcredist from qt installation but in VS 2019 image there is no vcredist in that path anymore, so maybe you know is it shipped within Visual Studio 2019 image? But if not, it's okay, I have workaround for that.

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 12 Mar, 2020 10:13 PM

   

   OK, you could install missing vcredist packages with the following PS script during the build:

   install:
   - ps: |
       iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/build-images/master/scripts/Windows/install_qt_module.ps1'))
       Install-QtComponent -Id 'qt.tools.vcredist_msvc2017_x86' -ExcludeDocs -ExcludeExamples
       Install-QtComponent -Id 'qt.tools.vcredist_msvc2017_x64' -ExcludeDocs -ExcludeExamples
   

   Also, similarly you can install 5.14.1 on VS 2017 and see how it works for you:

   install:
   - ps: |
       iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/build-images/master/scripts/Windows/install_qt_module.ps1'))
       Install-QtComponent -Version '5.14.1' -Name 'win32_msvc2017' -ExcludeDocs -ExcludeExamples
       ConfigureQtVersion 'C:\Qt' '5.14.1'
   

   or x64 version:

   install:
   - ps: |
       iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/build-images/master/scripts/Windows/install_qt_module.ps1'))
       Install-QtComponent -Version '5.14.1' -Name 'win64_msvc2017_64' -ExcludeDocs -ExcludeExamples
       ConfigureQtVersion 'C:\Qt' '5.14.1'
   

   More examples here: https://github.com/appveyor/build-images/blob/master/scripts/Window...

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 12 Mar, 2020 10:15 PM

   

   Updated script above with ConfigureQtVersion 'C:\Qt' '5.14.1'

   • Edit

7. 7 Posted by Mark Ts on 12 Mar, 2020 10:25 PM

   

   Thank you so much!

   • Edit

8. Support Staff 8 Posted by Feodor Fitsner on 16 Mar, 2020 12:09 AM

   

   Hi Mark,

   Have you got it working?

   • Edit

9. 9 Posted by Mark Ts on 16 Mar, 2020 11:24 AM

   

   Have you got it working?

   Yes, installation of qt 5.14. under VS2017 Image works perfectly for me, thank you!

   • Edit

10. Support Staff 10 Posted by Feodor Fitsner on 16 Mar, 2020 05:47 PM

    

    So, install script for 5.14.1 on VS 2017 worked for you?

    • Edit

11. 11 Posted by Mark Ts on 18 Mar, 2020 06:52 PM

    

    So, install script for 5.14.1 on VS 2017 worked for you?

    yes.

    • Edit

12. Support Staff 12 Posted by Feodor Fitsner on 18 Mar, 2020 07:17 PM

    

    Cool, thanks for the update!

    • Edit

13. Feodor Fitsner closed this discussion on 18 May, 2020 09:02 PM.