Complete.Org: Mailing Lists: Archives: freeciv-dev: May 1999:
Re: [Freeciv-Dev] Freeciv 1.8 bugs
Home

Re: [Freeciv-Dev] Freeciv 1.8 bugs

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Carsten Engelmann <carsten.engelmann@xxxxxxxxxxxxxxxxx>
Cc: freeciv-dev@xxxxxxxxxxx
Subject: Re: [Freeciv-Dev] Freeciv 1.8 bugs
From: Vasco Alexandre Da Silva Costa <vasc@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 4 May 1999 08:31:39 +0100 (WET DST)

On Mon, 3 May 1999, Carsten Engelmann wrote:

> Hi Vasco,
> 
> Vasco Alexandre Da Silva Costa wrote:
> > I haven't tried cygwin32 but with M$ Visual C++ 6.0 the client just
> > crashes for some reason.
> It would be very suprising if it worked.
> Networking and GUI are different with Windows compilers.
> The GUI would'nt be such a big thing but the networking is(for me).
> The rest of the code should compile giving you object files.

I know networking and GUI is different with Windows compilers because i've
coded in a mud server which had ports for Unix/Win32/Ami-TCP and i've used
gtk+-win32 for coding a Win32/Unix offline mud zone editor, so i've some
experience with that.

Winsock actually uses BSD sockets so network code isn't hard to port.  As
long as you don't use other Unixoid things, like pipes etc al there isn't
a problem.  Usually the porting work involves these translations (i may
be mistaken somewhere):

read    ->      recv 
write   ->      send
close   ->      closesocket

Also, you need to initialise the Winsock DLL when you start the program,
and you need to link the program with wsock32.lib or something.

---
Vasco Alexandre da Silva Costa, student @ Instituto Superior Tecnico,
Technical University of Lisbon - Software & Computer Engineering


[Prev in Thread] Current Thread [Next in Thread]