Mail Archives: djgpp/1998/10/22/14:47:29
Hello
I recently ported a sockets application (the Libnet library, in
fact) to RSXNTDJ, using the Winsock. I have it working at the
moment, but I had to make some changes to the supplied headers.
If anybody else has used Winsock from RSXNTDJ successfully, I'd
like to know whether they had to do what I have done, or whether
there's an easier (read: cleaner) way.
Firstly, RSXNTDJ's supplied winsock.h file does not seem to work
properly. It doesn't define any of the `select'-related types
and macros properly. I tried also including <sys/select.h> to
no avail -- that clashed with the winsock.h header. To resolve
all these problems, I copied another winsock.h file from a
documentation pack I have about the Winsock.
It seems dangerous to me to pass to the DLL socket lists
(fd_set) which are not what the DLL expects to receive.
RSXNTDJ's headers seemed to be doing this (if I was in fact
correct in including <sys/select.h>).
Secondly, I created the import library from wsock32.dll (which
was in my Windows `system' directory), not winsock.dll (which my
documentation pack was written for -- it's old documentation, I
know). Is this likely to cause any problems? I don't need any
of the fancy Winsock 2 features at the moment.
My last concern is that maybe Winsock 2 support is part of the
MSSDK. I have downloaded it, along with Doug Gale's patches,
but have not yet installed it. Since RSXNTDJ already had a
winsock.h file I assumed it was meant to support Winsock
programming without needing the MSSDK. Please correct me if I'm
wrong.
Thanks in advance for any information.
--
george DOT foot AT merton DOT oxford DOT ac DOT uk
xu do tavla fo la lojban -- http://xiron.pc.helsinki.fi/lojban/lojban.html
- Raw text -