Redis is made up on X64 DLL Settings, but from the win32 changed to 64 - bit program
At the time of 32 bit, is not a mistake,
But at the time of project 64 calls, or complains,
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: getsockopt has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: freeaddrinfo has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: setsockopt has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: select has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: getaddrinfo in ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: connect has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: accept already in ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: listen have been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: bind has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: getsockname has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: ntohs has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: htons has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: htonl has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: ntohl has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
4> Ws2_32. Lib (ws2_32. DLL) : error LNK2005: getpeername has been ServerCommon. Lib (Win32_FDAPI. Obj) defined in the
Look at the situation should be win32_interop. Lib is another name for a 32-bit processing, but in the X64 no,
Have a similar situation of the great god, for help how to deal with,

CodePudding user response:

64 May need 64 - bit libraries

CodePudding user response:

All have already took 64, libraries have succeeded, but in the project links, but there is a problem,

CodePudding user response:

In 64 project ignore ws2_32. Try the lib

CodePudding user response:

Can't, this is to be used, is there any other problems, ignore,
Is just the same kind of function, when the 32-bit win32_interop did alias processing,
But they didn't do a 64 - bit process, creates a redefinition

CodePudding user response:

reference 4 floor devilkillzzz response:

no, this is a must to be used, is there any other problems, ignore,
Is just the same kind of function, when the 32-bit win32_interop did alias processing,
But they didn't do a 64 - bit process, creates a redefinition

That is about to see if there is a support win64 build official source

CodePudding user response:

No, official things, 64 who have compiled, document also says, support 64 - bit, but not like a 32-bit corresponding function, alias processing (as such), so 64 although the library is successful, but after introducing project, links will have conflict,

CodePudding user response:

https://my.oschina.net/maxid/blog/186506

CodePudding user response:

From I install the WDK search ws2_32. Lib, ws2_32. Lib in two directory, amd64 and i386 X64 try amd64 directory

CodePudding user response:

Use the library in a 64 - bit this once again

CodePudding user response:

Hello, how do you solve this problem?

CodePudding user response:

Friend hello I now also encountered the same problem with this code can help you a lot hope things the compilation of a reward myself

CodePudding user response:

My QQ is 236554252 hope to get your reply