@Venkat_QT I did it. Thank you.

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

Hi, There's a pretty interesting Ars Technica article about netcode in fighting games. Worth a read.

I may have misunderstood the case that doesn’t work. Can you maybe do a small picture with the setup ?

@SGaist thanks!

@mounipanditi According to the Screens every thing is fine, but make sure that SFTP server is running in the target device so that application can be deployed into the target device.

@kshegunov ok now I understand! Thanks!

I'm just realizing that what I was trying to do was maybe nonsense : I was trying to pass on to the mysql server a value for the client on which my Qt program is running i.e. I was trying to "deceive" the server. And I could understand then that there would be no such method in QSqlDatabase (and that you couldn't understand my question initially). Could you confirm my reasoning please?

Just saw something, why are you using sudo ? That's not a good idea when you are building anything.

i think the only things you need to do is open or shutdown bluetooth, find bluetooth devices and connect if needed. all the other things must have been done by the hardware vendor

Got it. The documentation quite frankly is bad written when it comes to the QtCreatorDeployment.txt What you actually write in this file is just the remote path and without the sftp://IP_ADDRESS so now I simply have: /home/pi/Projects/ and the binary from my Debian 8 lands right in there on the RPi2. I posted a detailed explanation on stackoverflow (link in my first post).

Yes. It is a correct way but before the help engine can be used, it must be initialized by calling setupData(). QHelpEngine* helpEngine = new QHelpEngine("http://xxx.yyy/zzz/help.qhc", this); helpEngine->setupData(); Read more here: http://doc.qt.io/qt-4.8/qhelpenginecore.html#details