At 10:43 AM 12/23/2010, Richard Hipp wrote:
>I had to install zlib in \mingw\include and \mingw\lib but
>otherwise no changes were made to the MinGW installation.
>
>Windows users - please try this on your machines and let me know
>if you have problems. Thanks everyone for your help in fixing
>this problem.
It works over all, but I tweaked a couple of nits:
1. I don't like to modify mingw/lib or mingw/include because they
can get rebuilt from scratch when fussing with new releases of
MinGW. Since I got my build of zlib from GnuWin32 and installed
it with their installer, I changed Makefile.mingw to use a macro
to point at the GnuWin32 install folder, and used that macro to
construct the -I and -L options to GCC.
ZLIBDIR = C:/Programs/GnuWin32
ZLIB = -L$(ZLIBDIR)/lib -I$(ZLIBDIR)/include
2. You shouldn't need to name the Mingw include and lib folders
to GCC. The MinGW release of GCC will already know about those
locations.
3. The clean target uses a unix-style path name on the DEL
command line. I changed clean to look like:
del /q $(OBJDIR)
del $(APPNAME)
This works because a folder name is implicitly a wild-card for
all files in that folder, and the /Q option silences the query
about acting on that wildcard. I assume that typing "make clean"
is intent enough, and I don't need to be asked for more confirmation.
4. The install target still has an mv command, and names the
undefined macro INSTALLDIR as the destination. A reasonable
substitute on Windwos for mv is MOVE. There is no obviously ideal
default location to set for INSTALLDIR, however.
I used a fairly stale GCC (3.4.5 mingw special), but I wouldn't
expect to see any issues with a newer MinGW release.
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
