Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Conflict With winsock
#6
You directed me to:

You need to either:

1. make sure winsock2.h is always #include'd before winsock.h. Usually that means adding an #include <winsock2.h> statement before #include <vcl.h> and/or #include <windows.h> statements.

In every file where #include <vcl.h> and/or #include <windows.h> statements. occurs?

There must have been a change in compiler directives or somethign else. Why woulod it be working for 15 years?


2. add _WINSOCKAPI_ to your project's list of Conditionals to disable winsock.h globally.

Did not fix problem

3. add WIN32_LEAN_AND_MEAN to your project's list of Conditionals to prevent windows.h from using a #include <winsock.h> statement (amongst others).

Did not fix problem
Reply


Messages In This Thread
Conflict With winsock - by tultalk - 08-24-2018, 05:52 PM
RE: Conflict With winsock - by rlebeau - 08-24-2018, 09:59 PM
RE: Conflict With winsock - by tultalk - 08-26-2018, 02:17 AM
RE: Conflict With winsock - by rlebeau - 08-27-2018, 08:15 PM
RE: Conflict With winsock - by tultalk - 08-26-2018, 03:14 PM
RE: Conflict With winsock - by tultalk - 08-26-2018, 06:55 PM
RE: Conflict With winsock - by tultalk - 08-27-2018, 11:39 AM
RE: Conflict With winsock - by tultalk - 08-27-2018, 01:34 PM
RE: Conflict With winsock - by tultalk - 08-28-2018, 02:24 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)