For latecomers, you could keep track of this issue here: https://bugreports.qt.io/browse/QTCREATORBUG-32283

@Pl45m4 I apologize for my incomplete explanation. What I meant to say is exactly this:

I created a project and build/run settings which includes path of destinations, executables and qmake settings. When I publish my project to another person all the settings I created are missing. As you said pro.user file shouldn't shared between projects or used on other systems. But As I read in qt documents it says pro.shared file could be shared for make projects settings portable. The problem is I wrote this file and I can share my settings to another system, but every time I need to change the version and set the current path of project for build/run configurations.
Here is an example:

C:\Users\duruk\Desktop\Sample\build

This is the target path of my Press_Release build configuration. As you see this path is unique for my system (name of project is Sample, this folder contains pro file and pro.shared file). I have written a bash file to changing the paths to current paths, and a manual for describing how to user could set configuration. This is the bash file I wrote to changing paths:

DOSYA="Sample.pro.shared" OLD="xxxxx" NEW=$(PWD) if [ ! -f "$DOSYA" ]; then exit 1 fi sed -i "s|$OLD|$NEW|g" "$DOSYA"

Well now I'm searching a way to settings project path automaticly and and prevent changing ProjectExplorer.Project.Updater.FileVersion variable every time project moved another system. Is there anyway to share settings more easy and effective?

The documentation of the method I tried:

https://doc.qt.io/qtcreator/creator-sharing-project-settings.html

Thank you for your reply.

This issue was fixed in Qt Creator 11.0.1.

@SGaist I was too sure I guess... :-)

Thanks!

It took sometime to figure out the missing library.
It seems the qt-creator package does not install some of the libraries.

I had to install the following library package using the package manager to get the functionality working:

qml-module-qtquick-controls2

It would bet great if the qtcreator GUI itself reported about the missing libraries.
Instead of dumping it on the console.

I completely forgot to ask if this is even the "usual" or "preferred" way to cross build, deploy and remote debug?

My only concern is to start with the start script, so the executable itself and the called command actually differ

@nwoki
Hi
It means even it reports thats its QtWidgets that crashes, its likely not that DLL
if a plain empty GUI project works. ( for exact same folder , same pc)
I would next add some openGL to the test project see if it still runs.
As it seems might be direclt related to Qt ( like wrong Qt dll loaded)
so it could be the openGL for clients gfx card.

Your listing does not contain any error message. Search for it above the given output.

Qt Creator build questions are best asked on Qt Creator mailing list. That's where devs working on it reside.

@aha_1980, thank you for your answer!

This was indeed the problem. The library was compiled with Visual C++.
I changed the compiler in Qt Creator and the problem was solved!

Thx a lot, you helped me!