[GRASS5] Cygwin build of Grass5
John Huddleston
jhudd at lamar.colostate.edu
Mon Sep 4 11:22:12 EDT 2000
Hi Eric,
No shared (DLL) libraries are being built. The binaries
both .a and .exe are placed under the /usr/local/grass-5.0b
area as well as all the other support files during the gmake5
process. It builds the same as the Unix build. Except for
executables with .exe, all the files look like Unix files.
I guess the major secret is that I added a Gmakefile in all
the directories where they did not exist. The lines in the
Gmakefile are
all:
$(MAKEALL)
That's most of it. I ran the testgrass.sh and it passed all
except for the last which was supposed to fail. Actually,
I would like Markus, and others, to add more to the testgrass.sh
to verify that all programs will run.
John Huddleston
----- Original Message -----
From: "Eric Mitchell" <emitchell at altaira.com>
To: <grass5 at geog.uni-hannover.de>
Sent: Tuesday, August 29, 2000 8:27 AM
Subject: Re: [GRASS5] Cygwin build of Grass5
>
> John,
>
> Part of the problem is knowing what to check for in the
> autoconf part of the make process. Are you building
> shared libraries (DLLs)?
>
> Part of my Makefile strategy is to rely on generic rules
> that are included from makefiles in a "well-defined"
> location. I have fairly generic rules in there, but they
> may need tweaking for Cygwin builds. If you have a log
> of the build process, I'd love to have it around for
> reference, to make sure my generic rules can be tweaked
> accordingly.
>
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'
More information about the grass-dev
mailing list