[GRASS5] new directory structure?

Markus Neteler neteler at geog.uni-hannover.de
Mon Feb 12 06:02:58 EST 2001

On Sat, Feb 10, 2001 at 03:37:08PM -0800, Eric G . Miller wrote:
> On Sat, Feb 10, 2001 at 03:36:18PM -0700, bakerwl wrote:
> > Hello,
> > 
> > After installing beta11, I'm a little confused about the new
> > directory structure.  Maybe I did something wrong, or maybe
> > one of the "make clean" variations fixes this.
> > 
> > It looks like I get identical copies of the /bin /bwidget /documents 
> > /driver /etc ...and so on directories in both:
> > 
> > /usr/local/grass5
> > /usr/local/grass5/grass5.0beta11_src/dist.i686-pc-linux-gnu/
> > 
> > I just put the *.tar.gz in /usr/local/grass5 and unzipped/untarred
> > then went into grass5.0beta11_src and ran:
> > ./configure
> > make
> > make install
> > 
> > ??
> Yes, this is "correct".  Essentially the set-up builds everything into
> $(SRC)/dist.$(ARCH).  "make install" basically copies this to the final
> destination.  Given the way gmake5 and the sources are set-up, this was 
> a work around to allow a full build to be done (as any old user) and
> then the install to be done as a priveledged user.
> It probably would be better if each Gmakefile built its final modules in
> OBJ.$(ARCH) and then there was an "install" target, but I don't think
> the gmake5 setup will work this way (not sure).  That's probably how
> grass5.1 will work.

To overcome this problem in 5.0, Huidae Cho has been implementing
gmake5 -i

If the module was already installed etc, you can use the flag to
get an updated modules into the final place without running the 
entire make install process again. It directly copies the updated
module from dist.$ARCH to /usr/local/grass/... or wherever your
grass5 lives. Nice feature, just try it.


 Markus Neteler

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