<HTML
><HEAD
><TITLE
>Acquisition/Compilation of GRASS Source Code</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.56"><LINK
REL="HOME"
TITLE="The Geographic Information Systems: GRASS HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Acquisition/Installation of GRASS4.1.5 Binaries"
HREF="install415.html"><LINK
REL="NEXT"
TITLE="GRASS 4.2 Quick Start"
HREF="quickstart42.html"></HEAD
><BODY
CLASS="APPENDIX"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Geographic Information Systems: GRASS HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="install415.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="quickstart42.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="APPENDIX"
><H1
CLASS="APPENDIX"
><A
NAME="COMPILING"
>C. Acquisition/Compilation of GRASS Source Code</A
></H1
><P
> The GRASS binaries for Linux tend to work. Why would anyone want to mess with
the source code?
</P
><P
> Let's try to answer this with another question: "Why can't I get the
source code to my GIS, so I can see how it works, and maybe fix some
things to work the way I like them?" (You probably know the answers
to this question, at least for many commercial software packages.)
</P
><P
> If you want to
</P
><P
></P
><OL
TYPE="1"
><LI
><P
> Add any of the numerous existing alpha and contributed GRASS functions,
</P
></LI
><LI
><P
> Understand how a function works (did any programming shortcuts or
performance enhancements affect the accuracy of a function? Can
I improve the performance of a function?)
</P
></LI
><LI
><P
> Revise or enhance the code (if you do this, please see Appendix D!),
</P
></LI
><LI
><P
> Try compiling several tens of megabytes of source code,
this appendix is for you. Also check Appendix E.
</P
></LI
></OL
><P
> First, you need to acquire the source code, and the GRASS Installation
Guide. You may also want to get the GRASS Programmer's Manual and
User's Reference Manual. To do this:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>ftp moon.cecer.army.mil
login: anonymous
password: your email address
cd pub/grass/grass4.1/release/source
get README.4
get README.5
image
mget s4* (or s5*, your choice)
cd ../../documents
get installGuide.ps.Z
cd /manuals/programmer/postscript
get progman.ps.Z
cd ../../user/postscript
get refman.ps.Z
bye
</PRE
></TD
></TR
></TABLE
><P
> Don't forget this site. There are several tutorials on some of GRASS'
more advanced programs in the pub/grass/grass4.1/document directory.
There are two options for source code (I'm only discussing GRASS
version 4.14 here, though version 4.15 is also available) The
pub/grass/outgoing directory contains many contributed functions (and
many other candidates for enhancing your system).
</P
><P
> Follow the README.4 file for installing GRASS version 4.14 (which is
sometimes called version 4.1.4) source code. Follow the README.5 file
for installing GRASS version 4.15 (which is sometimes called version
4.1.5) source code.
</P
><P
> After installing the source code, uncompress and print
installGuide.ps.Z (or the troff version, if you prefer that and got it
from a neighboring directory). You might also want to uncompress and
print refman.ps.Z and progman.ps.Z at the same time. Note that
progman.ps.Z is called the programmer's manual, but also contains
valuable information about data formats and directory structures.
Advanced users may also want to know the GRASS system utilities, even
if they won't be calling them in code.
</P
><P
> Now, use the GRASS Installation Guide (from installGuide.ps.Z) to
guide yourself through the installation. The thickness of this
document may at first be intimidating. However, if you installed
Linux yourself, you should be ready to tackle a GRASS installation.
Don't be surprised if a function or two does not compile on your
system. I have a couple of uncompiled functions on my own Linux
system. Fortunately, these are functions that I don't use... Some
day I'll get back to them, fix them, and compile them!?
</P
><P
> Here is a late-breaking addition, on how to install the newly released
<A
HREF="http://www.baylor.edu/~grass"
TARGET="_top"
><I
CLASS="CITETITLE"
>GRASS 4.2</I
></A
>
from
<A
HREF="http://www.baylor.edu"
TARGET="_top"
><I
CLASS="CITETITLE"
>Baylor University</I
></A
>
This text is as provided by Baylor, unedited by myself due to its release only a few
days ago. Please note the similarity with other installations..
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="install415.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="quickstart42.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Acquisition/Installation of GRASS4.1.5 Binaries</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>GRASS 4.2 Quick Start</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
