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 !

I saw this old thread of mine and remembered, that the issue was solved. Just writing to explain how I solved it. The problem was in the proxy settings. People who had their proxy configuration to automatic could connect, everyone else could not. First solution was to set the configuration to automatic on every client. Which was cumbersome and seemed stupid, because the program does not need any proxy. A little later I found out, that there was a problem with the Qt Network Interface, it was a known bug and could be worked around by telling the program manually to not use any proxy: /* call before connecting to network. Easiest way is, just call somewhere at the beginning of the program */ QNetworkProxy::setApplicationProxy(QNetworkProxy::NoProxy);

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