After running windeployqt the application does not start

cupressus

Hello,
i have build a simple qml app. The app runs well inside the qt enviroment.
Running windeployqt shows files you can see in the attached picture.
The deployment shows no errors. But starting the executable does nothing.
Not even an error is displayed.
Can anybody help me. Thanks in advance.![alt text]

Using qt-5.14.2

SGaist

Hi and welcome to devnet,

What parameters did you pass to windeployqt ?

cupressus

Hello, thanks for prompt reply. I used no parameter. I only specified the path to the application.exe.

SGaist

Then you should use that --qmldir option to point to your QML sources.

cupressus

With option --qmldir still the same. .exe does not start.

CP71

@cupressus
Hi
Do you have more versions of Qt framework?
If yes, are you sure to run right windeployqt?
Always if yes, Check Qt DLLs that must be aligned with your application.

J.Hilk

@cupressus said in After running windeployqt the application does not start:

With option --qmldir still the same. .exe does not start.

please post the argument you used for the tool, I think you did not add the actual path to your qml files after adding --qmldir

CP71

@cupressus
Hi,
I reproduced your issue.
I run windeployqt with debug application.
Is possible your application is in debug compiled?

cupressus

C:\Users\alois\Documents\build-untitled1-Desktop_Qt_5_14_2_MinGW_32_bit-Release\release

within release directory stays my executabe named untiteld1.exe

cupressus

@cupressus said in After running windeployqt the application does not start:

C:\Users\alois\Documents\build-untitled1-Desktop_Qt_5_14_2_MinGW_32_bit-Release\release\untitled1.exe

JonB

@cupressus
Try running a dependency walker (https://www.dependencywalker.com/) on your .exe to see if you can spot any potentially missing/not found/wrong bit-ness DLLs on the target system. Also if you are not already doing so try running your executable from a Command Prompt rather then double-clicking it, Windows might be outputting some kind of message which you could see there.

cupressus

Hello, have a look at the attached picture. This is what dependency walker shows.

cupressus

I have found the error. I did a mistake specifying the path to qml files. Now it works.
Nevertheless i am wondering that there ar so much files needed for this simple app.
125mb?

J.Hilk

@cupressus look at that, had you done as I asked

please post the argument you used for the tool,

we might have been here earlier.

The files will be big, OpenGL.dll will be 20 mb is alone.
That said 128mb is a lot and more than I would expect, but without more information hard to tell/advice

cupressus

@J-Hilk

here the command line i used for deployment:

windeployqt --qmldir c:\qt\5.14.2\mingw73_32\qml c:\myApp\myApp.exe

Yes i can delete some files step by step and look what happens but i cannot imagin
if there is not another way.

J.Hilk

@cupressus said in After running windeployqt the application does not start:

windeployqt --qmldir c:\qt\5.14.2\mingw73_32\qml c:\myApp\myApp.exe

ah, an error that I expected, you gave the tool the path to the whole QML folder of your Qt installation therefore it got everything qml related -> your folder is so big now.

That path should be to the top most folder of your created QML files.

Lets assume, your top most QML File is named MySuperAppMain.qml and it has the following path c:\MyQtProjects\MySuperApp\MySuperAppMain.qml

than your argument should be:

--qmldir c:\MyQtProjects\MySuperApp

cupressus

@J-Hilk , thanks that helped. The installation folder is now a bit smaller but still
97mb.

cupressus

I was now able to reduce the amount to 50 mb thats ok. for me.

Thanks for help.

Samuel Alves

@cupressus I used the same commando to deploy my application but when i try to run nothing happens.

The command: C:\Qt\5.15.2\msvc2019\bin\windeployqt.exe --qmldir C:\Qt\5.15.2\msvc2019\qml C:\Users\Samuel\Desktop\deploy\main.exe

SGaist

@Samuel-Alves Hi and welcome to devnet,

You have to give the path to your qml sources. The ones that you have in your sources not the one from Qt.