I also played around with the WSFU and have found a number of things in it
that make it less interesting than a native Windows compile. Buried in
the documentation are some notes about how it works and it is clear that
an AOLserver compiled under SFU will perform slightly more slowly than
compiled natively for Windows. I also could not figure out how to build
Tcl with threads enabled. I did find some notes about building a Unix
command line application so it could run natively in the Windows command
line compiled against Windows DLLs.
It looks to me that SFU is designed, as it states in the "sales"
literature, to make it easy to integrate Windows boxes into a Unix
environment. It is not designed to support building and running Unix code
on a Windows box, even though this is possible to do.
/pgw
"Kevin S. Davis" <[EMAIL PROTECTED]>
Sent by: AOLserver Discussion <[EMAIL PROTECTED]>
07/13/2004 08:40 AM
Please respond to AOLserver Discussion
To: [EMAIL PROTECTED]
cc: (bcc: Greg Wolff/BNA Inc)
Subject: Re: [AOLSERVER] Windows Services for UNIX
By pure coincidence I happened to try compiling AOLserver under WinSFU
last night...
First, yes, SFU basically seems to be a Microsoft proprietary Cygwin.
Of note, they do not include X. All of the x* bins are in there, e.g.
xterm, but the actual Xwindows server is not included. You have to buy
Xwin32, Exceed, or something else.
As for AOLserver under such an environment... The optional TCL binaries
and libraries for SFU, which are downloaded separately from
interopsystems.com, were not compiled with threads enabled so the
AOLserver compile chokes. You can download their version of the TCL
source from interop, but it seems to be practically identical to the
official TCL source tarball. I tried to compile both and got the same
errors. Configuring under the win tree chokes because 'windres' is
missing. I'm not really a Windows guy and I don't know what 'windres'
is. The unix tree will configure but won't compile due to some kind of
timezone error.
It was time for bed at that point, so I gave up. It seems to me it
should be possible to compile AOLserver under this configuration. It
just requires some hacking-out-of-the-box.
Cheers,
Kevin
Nathan Folkman wrote:
> http://www.microsoft.com/windows/sfu/
>
> Just curious, has anyone tried compiling and running AOLserver in this
> environment on Windows?
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
