[omniORB] Switch to use Winsock 2 in omniORB4?

[Sai-Lai Lo]

I've switched to use winsock2 since nobody seems to mind :-) The changes
will appear in tonight's snapshot.

There are 2 notable changes that win32 users must note:

1. As required by the winsock 2 library, the compiler pre-processor
flag -D_WIN32_WINNT=0x400 is added. The omniORB4 make variables has been
updated accordingly.
2. The link option wsock32.lib is changed to ws2_32.lib mswsock.lib.

You will have to modify your MSVC++ project setting to include these
changes.

Let me know if this causes any problems.

Regards,

Sai-Lai



----- Original Message -----
From: "Sai-Lai Lo" <s.lo@uk.research.att.com>
To: "omniorb list" <omniorb-list@uk.research.att.com>
Sent: Thursday, August 23, 2001 5:50 PM
Subject: [omniORB] Switch to use Winsock 2 in omniORB4?


> I'm thinking of switching to use the Winsock 2 API in omniORB4. This is
> because I would like to use the equivalent of ioctl SIOCGIFCONF on win32
to
> get the information about the network interfaces available.
>
> AFAIK, the equivalent in Win32 is SIO_GET_INTERFACE_LIST but this is only
> available in winsock 2.
>
> If I'm going to use that, it will mean that the ORB has to be linked with
> the Winsock2 DLL instead of wsock32.dll.
>
> I wonder if this will cause problems for applications if the rest of the
> code is compiled with winsock v1.1. Does anyone have any view on this? Any
> objections and the reasons why are most welcomed.
>
> Please speak up asap for I'll have to do something rather quickly.
>
> Regards,
>
> Sai-Lai
>
>
>
>