Cygwin has limited support for Posix threads. You can check the Cygwin FAQ at http://cygwin.com/faq/faq.html to see which functions are missing. Several of the functions that AOLserver 4.x uses aren't in the DLL yet, making any port at this time difficult. In response to Dossy's question, I don't think many people run production servers under Cygwin. My guess is that most Windows AOLserver users are trying to duplicate a part of their site on their laptop, or they want to experiment with OpenACS without installing Linux, etc. For that sort of non-production application, the overhead introduced by Cygwin isn't a concern. I believe the Visual Studio project files for AOLserver 3.4 have some problems. (Incorrect paths to files, bad settings for debugging, etc.) That may be why some people are reluctant to build the core from source even if they have all of the tools and want to build modules. You could perhaps zip up the lib files in a separate download for those people? Of course, I ended up having to build from source anyway to incorporate some of the ADP patches that are on SourceForge. I've been using a patched version of 4b1 on Windows 2000, and the nscgi module is working for me. I checked it out of the AOLserver repository with -D 2001-11-04. My personal experience has been that 4b1 is as stable on Win2k as 3.4 is. Building the source is a pain, but I have notes that I will share if you are willing to attempt it. My work was related to an OpenACS 4 installation, so some of the patches aren't strictly necessary just to get AOLserver running. I think the nscgi in http://acs-misc.sourceforge.net/ns_rel_beta2.html works as well, if you can't / don't want to build from source.
Jamie At 11:01 PM 12/17/2001 -0500, Dossy wrote: >On 2001.12.17, Tom Poindexter <[EMAIL PROTECTED]> wrote: > > Perhaps a few modules too, postgres and nsodbc for starters. > >I'll leave that as an exercise to the reader, at least initially. > > > If it is as simple as 'configure; make' with Cygwin, then knowing that > > would be helpful too. > >No, it isn't. Perhaps in 4.0 when Win32 support is "dropped" I might >consider a porting effort to make 4.0 run under Cygwin, but IMHO the >overhead of Cygwin just makes the idea so unattractive. > >Do people seriously run production servers under Cygwin? *shudder* > > >On 2001.12.17, Ramin Naimi <[EMAIL PROTECTED]> wrote: > > Since you asked, I installed the 3.4.2 version (win32) and found there were > > a number of binaries missing (such as nscgi.dll). Also, is there a new > > ASxx-win32-install which includes the source, in particular the VC > workspace > > and projects? > >You mean 3.4, not 3.4.2 version -- there IS no binary distribution >of 3.4.2. > >Yes, nscgi.dll was missing because nscgi under Win32 in AOLserver 3.4 >seems to be completely broken (at least for the very, very cursory >testing I did). I felt it wasn't worth including if it wasn't >working for even the most simplest CGI tests. > > >On 2001.12.17, Wojciech Kocjan <[EMAIL PROTECTED]> wrote: > > Maybe you should also put a distro with .lib files for easier module > > recompilation :) > >Why bloat the binary distribution with unnecessary files? > >If you're going to compile modules, then you've got a compiler. >Then, just build AOLserver from source. Why should I bother >packaging up the .lib files, then? > >The binary install should only have enough in it for people >who are only running a binary install. If you're going to >compile from source, then just compile everything from source. > > > I once tried compiling nshello with MSVC++ and gave up... > >Sorry to hear that. > > >-- Dossy > >-- >Dossy Shiobara mail: [EMAIL PROTECTED] >Panoptic Computer Network web: http://www.panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70)
