This problem occurs because windows.h itself contains winsocks.h/winsocks2.h and vise versa.== So just include any one of them should be fine.== Do not add any other macros to try to solve this problem like most of the people tell me to do on the Internet. They will only cause troubles!
2017/2/9 22:53