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)
