[GRASS5] ODBC driver build problem

Eric G. Miller egm2 at jps.net
Fri Aug 10 11:29:50 EDT 2001

On Fri, Aug 10, 2001 at 09:05:20AM -0400, Frank Warmerdam wrote:
> What is gmake5 under the hood?  Is it just a script setting up makefiles
> for old style (non-GNU) make?  If we were willing to specify GNUmake
> as a build requirement we could have the makefiles decide what subdirs to
> build based on variables setup by configure pretty easily.  
> Amoung other problems, the existing Gmakefile and list of places to
> build is hard to grok for developers new to GRASS.  

The plan was to completely redo the build system in 5.1.  At least one
of the goals of that process it to build shared libraries (when the
architechture allows) so that the resulting binary set can be much
smaller.  Improving modularity of the build system is also a goal.

> A few other "developer" questions:
> o How do folks normally do quick global builds when they just want to
>    refresh things.  I find the current mechanisms insistance on 
> reprocessing
>   all the html/man stuff makes it very slow to do a top level make.

Yes. Very slow.  Takes about an hour or so on my 'puter to do a clean

> o Do developers normally do a "make install", and run from the 
> installed tree
>    during development, or somehow run directly from their build tree?  
>    When I am just making iterative improvements to a program I have adopted
>    the practice of just doing a gmake5 in that programs directory, and 
> replacing
>    the binary in the installed tree with a link back to the executable 
> in the
>    build tree.  But this is somewhat tedious to steup, and I would 
> presume other
>    folks have a smoother approach.

For small changes, I just do gmake5 and copy the binary from dist.<foo>
to wherever it would live in <target>/grass5/.  Somewhat tedious to be
sure.  When libraries change, it's another matter...

Eric G. Miller <egm2 at jps.net>

More information about the grass-dev mailing list