Including sio_socket.h and compilation wit clang fails. about socket.io-client-cpp HOT 6 CLOSED

Yes i did. Problem is that i always use cmake.
I found them problem. boost signals do not work together with those of qt. I had to specify no_keywords in cmake like this:
ADD_DEFINITIONS(-DQT_NO_KEYWORDS) #makes boost signals work together with qt's when using cmake
Excellent library, melode11, much appreated. bows

from socket.io-client-cpp.

q

Yes i did. Problem is that i always use cmake. I found them problem. boost signals do not work together with those of qt. I had to specify no_keywords in cmake like this: ADD_DEFINITIONS(-DQT_NO_KEYWORDS) #makes boost signals work together with qt's when using cmake Excellent library, melode11, much appreated. bows

qmake like that: DEFINES += QT_NO_KEYWORDS in *.pro file.

from socket.io-client-cpp.

Also minor thing in your readme:
//emit event name only: socket->emit("login"); //emit text h.socket()->emit("add user", username);
should be
//emit event name only: h.socket->emit("login"); //emit text h.socket()->emit("add user", username);

from socket.io-client-cpp.

Thanks for reporting, but it seems OK on my clang.
Did you add c++11 options on your compiler.

from socket.io-client-cpp.

I can't use the solution mentioned above because it appears to break Qt's signals. Also, I'm using gcc 4.8.5, not clang as in the original issue. Is there an alternative, straightforward fix for this compiler error?

from socket.io-client-cpp.

q

Yes i did. Problem is that i always use cmake. I found them problem. boost signals do not work together with those of qt. I had to specify no_keywords in cmake like this: ADD_DEFINITIONS(-DQT_NO_KEYWORDS) #makes boost signals work together with qt's when using cmake Excellent library, melode11, much appreated. bows

qmake like that: DEFINES += QT_NO_KEYWORDS in *.pro file.

nice~this suggestion works!
tks

from socket.io-client-cpp.