2011 21:21
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Progress in Aolserver
Hi,
As Dossy mentioned, we spent some time trying to support the win32 port.
That included a goofy Tcl-based config thing (which also helped to verify a
workable Tcl installation) and a dose
] On
Behalf Of Jim Davidson
Sent: 03 August 2011 21:21
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Progress in Aolserver
Hi,
As Dossy mentioned, we spent some time trying to support the win32 port.
That included a goofy Tcl-based config thing (which also helped to
verify a workable Tcl
Maurizio Martignano wrote:
Well… ehm... the version in the tar ball compiles and runs well under
Windows…
Not so for the version under CVS HEAD: many of the changes introduced
have been implemented with a careful eye only for *nix, and not for Windows.
By looking at the code I have the
I speak only for myself ...
I personally have thoughtfully cared for the Windows support in
AOLserver -- once upon a time, I had built the Windows binaries that
some folks were using. Through discussions I had with Jim Davidson, the
new build mechanism for AOLserver 4.5.x was meant to make
Hello all,
Some few clarifications, I am afraid I wasn't clear.
The compilation in itself was rather simple and went almost ok.
The issue was in the behavior in the testing
Some of the code, eg, function calls to the networking parts and so on, are
working in the tar ball
Hi,
As Dossy mentioned, we spent some time trying to support the win32 port. That
included a goofy Tcl-based config thing (which also helped to verify a workable
Tcl installation) and a dose of ifdef's and compatibility code. In general,
the AOLserver code base is decidedly Unix -- any Win32
application, having it running also on Windows may be very helpful.
Cheers,
Maurizio
-Original Message-
From: AOLserver Discussion [mailto:AOLSERVER@LISTSERV.AOL.COM] On Behalf Of
Jim Davidson
Sent: 03 August 2011 21:21
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Progress
