Dear all,
I'm the maintainer of the Windows Port of OpenACS.
Recently (22/07/2011) I got the CVS HEAD version of Aolserver and compiled
it with Microsoft Visual Studio 10 for Windows 32 bit and Windows 64 bit.
I did this because I wanted to take profit of the mods
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
Hi Jim,
Once again I'll take ]project-open[ as example.
Please look in here:
http://sourceforge.net/projects/project-open/files/project-open/V3.5/
How big is the Windows Installer (which installs on both Windows 64 and
Windows 32 systems)?
How big is the VMware Image?
Well in some