They are in the sources you already cloned.

@Dean21 @JoeCFD asked where the mqtt libs you built are stored, not where the code is...

@SGaist Great Thank you this, I know that qt has its own MQTT module just I had already developed my code for MQTT using the mosquitto library before I knew I was going to be making a GUI using QT.

As I already wrote, use the full path to qmake. Otherwise you are going to use your distribution provided Qt.

Hi,

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

@Milav said in segmentation fault:

the difference between host pc and Embedded target board is only QT source.
Host pc => qmake (qt version 5.4.0 )
Embedded target => qmake (qt version 4.8.7)

You should have stated these settings from the very beginning... :-)

Anyway, could it be possible that you build Qt 4.8.7 for PC (host) and build your example again with that Qt version and run in PC to see what happens.

@lopeztel said in Property of object is not a function:

This is what happens when you spend hours staring at the screen ...

Sometimes when you have had too much to think you need a break and coffee.

@SGaist Thanks a lot! I know there was something simple I wasn't seeing

Glad you found out and thanks for sharing !

@Pablo-J-Rogina yes, and it doesn't say much more than what can be gleaned from the function signature. What is missing is any discussion of why one might want to call it (in normal circumstances that is, not to work around what apparently is a bug). Also, as I asked, whether calling it might have any adverse effects.

On a side note, the getter should be const, it doesn't modify anything in the class instance.

Hi and welcome to devnet,

Qt has not a module for that that you can clone from here. You can build it as any other Qt module: qmake && make && make install.

IIRC, background services with Qt are part of 5.7