On Thursday, 01 Nov 2001, Guy Harris wrote:
> > I finally got it built and tested under windows, and it works great!
>
> Cool. Do you have patches to "Makefile.am" and "Makefile.nmake" as
> well?
They were in the original patch. Nothing in them changed to build under
Windows. (At least I got that part right) Do you want me to regenerate
the patch?
> > BTW - I know I haven't said it enough . . building under windows BLOWS. Thank
> > God I had cygwin installed to do little things like run yacc and flex . . .
>
> Yup, that's why we note, at the end of README.win32:
>
> If you don't have a Unix system handy, most of those tools are
> available for Win32 systems as part of the Cygwin package:
>
> http://sourceware.cygnus.com/cygwin/
>
> After installing them, you will probably have to modify the
> config.nmake file to specify where the Cygwin binaries are
> installed.
>
> (Of course, another reason why I like having Cygwin installed at home is
> that I can use the command line in the ways that I'm used to doing on a
> UNIX box....)
Yeah. I *love* cygwin. But, I thought the README.win32 wasn't quite enough.
Mabye I'll add to it from a newbie's perspective. Running MSVC batch files,
putting libraries/etc in the right place, editinging config.nmake, running
cleanbld.bat, etc took a while to figure out, and get working..
Plus, if you run nmake from Dos (CMD.exe), where it can't find sed, it
barfs and creates partial config files that don't work right. It's really
strange. (The worst part is, ./configure does *almost* work. I took that
path initially, and ran into many problems. Eventually it would be really
cool to build it completely under cygwin with gcc)
I had to keep going back and forth from cygwin to CMD to get
things right. But, it *did* eventually build. (And, then, I had to move
all the DLLs somewhere in the path, and it actually worked! Although, the
DNS lookups seemed MUCH slower than under linux)
-Dave
