[GRASSweb-list]scott: web/macgrass macgrass.html,1.5,1.6
grass at intevation.de
grass at intevation.de
Wed May 5 19:15:25 EDT 2004
Author: scott
Update of /grassrepository/web/macgrass
In directory doto:/tmp/cvs-serv15557
Modified Files:
macgrass.html
Log Message:
minor updates and cosmetics
Index: macgrass.html
===================================================================
RCS file: /grassrepository/web/macgrass/macgrass.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- macgrass.html 26 Mar 2004 16:12:50 -0000 1.5
+++ macgrass.html 5 May 2004 23:15:22 -0000 1.6
@@ -1,76 +1,79 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
-
+
<DEFANGED_meta content="text/html; charset=iso-8859-1"
http-equiv="Content-Type">
-
+
<DEFANGED_meta content="Scott Mitchell" name="Author">
-
+
<DEFANGED_meta content="GRASS, GIS, Macintosh" name="KeyWords">
-
+
<DEFANGED_link href="../sitestyle.css" type="text/css" rel="stylesheet">
<title>GRASS GIS 5.0 on Macintosh Information</title>
</head>
<body>
-
-<center>
-<h1>
+
+<center>
+<h1>
<hr width="100%" noshade="noshade" size="3">GRASS 5 on Mac OS X</h1>
- <b>N.B. This document is preliminary, incomplete, and goes out of date
-with alarming frequency. Please contact Scott Mitchell ("smitch at mac.com")
-with suggestions or questions about the document.</b><br>
- (DRAFT version - Mar 5, 2004)<br>
- <br>
- </center>
-
+ <b>N.B. This document is preliminary, incomplete, and goes out of date
+ with alarming frequency. Please contact Scott Mitchell ("smitch at mac.com")
+ with suggestions or questions about the document.</b><br>
+ (DRAFT version - Apr 28, 2004)<br>
+ <br>
+ </center>
+
<p> </p>
-
-<hr width="100%" noshade="noshade" size="3">
+
+<hr width="100%" noshade="noshade" size="3">
<h1>GRASS GIS on Mac OS X<br>
- </h1>
- GRASS on Mac OS X shares all the functionality enjoyed on other UNIX- or
-Linux-based platforms. There are quirks to the operating system that
-occasionally pose challenges when new features are added or changed in the
-GRASS source code, but these are usually sorted out promptly. In addition,
-due to the fact that Mac OS X has evolved quite differently from other UNIX
-systems, there is a variety of ways to get GRASS installed on a Mac.
-This page is an attempt to help you navigate through the options. Some
-assumptions are made about your familiarity with GRASS, in that we are not
-re-explaining things here that are found in other pages on the GRASS web
-site.<br>
- <br>
- <br>
-
+ </h1>
+ GRASS on Mac OS X shares all the functionality enjoyed on other UNIX-
+or Linux-based platforms. There are quirks to the operating system
+that occasionally pose challenges when new features are added or changed
+in the GRASS source code, but these are usually sorted out promptly.
+In addition, due to the fact that Mac OS X has evolved quite differently
+from other UNIX systems, there is a variety of ways to get GRASS installed
+on a Mac. This page is an attempt to help you navigate through the
+options. Some assumptions are made about your familiarity with GRASS,
+in that we are not re-explaining things here that are found in other pages
+on the GRASS web site.<br>
+ <br>
+ <br>
+
<h1>Main Issues: UNIX/X11-based or Aqua-based ?<br>
- </h1>
- No matter which method you choose to get GRASS working on your system, the
-following issues may come up. MacOS X has a split heritage - the user
-interface that came from the marriage of Apple and NeXT, and the UNIX tradition
-that came in through FreeBSD. This means that there are multiple alternatives
-for developing user interfaces to applications. GRASS comes from a
-UNIX and X11 heritage. The tools that are used in the standard (i.e.
-shared with other platforms) GRASS user interface are now all readily available
-on the Mac, but there are also alternatives. <br>
-<br>
-Therefore, building GRASS requires a decision on whether or not GRASS will
+ </h1>
+ No matter which method you choose to get GRASS working on your system,
+the following issues may come up. MacOS X has a split heritage - the
+user interface that came from the marriage of Apple and NeXT, and the UNIX
+tradition that came in through FreeBSD. This means that there are multiple
+alternatives for developing user interfaces to applications. GRASS comes
+from a UNIX and X11 heritage. The tools that are used in the standard
+(i.e. shared with other platforms) GRASS user interface are now all readily
+available on the Mac, but there are also alternatives. <br>
+ <br>
+ Therefore, building GRASS requires a decision on whether or not GRASS will
use features that are exclusive to Apple's graphic interface ("Aqua").
This allows more seamless integration in to the Apple environment, but requires
work "outside" of the main GRASS development to make it work. If you
use the <a href="http://www.r-project.org">R statistics package</a>, this
may sound familiar - there have long been projects alongside the main development
-stream to enhance R by using capabilities of the Mac environment. For
-GRASS, such work has been concentrated in the efforts of Joshua Lecock's
-<a href="http://openosx.com/grass/">Open OS X port of GRASS</a>, which uses
+stream to enhance R by using capabilities of the Mac environment.
+For GRASS, such work has been concentrated in the efforts of Joshua Lecock's
+ <a href="http://openosx.com/grass/">Open OS X port of GRASS</a>, which uses
an Aqua version of the Tcl/Tk interface so that the menuing system has a
consistent look and feel to other Macintosh products. It also provides
a software installation CD, subscription and support options, and various
-bundles with other traditonally-UNIX software packages. A <a href="grasstep.sourceforge.net">Sourceforge project for porting GRASS to Quartz and GNUstep</a> has also been started, and is looking for programmers, if you have the skills and interest.<br>
- <br>
- The alternative approach is to stick with the X11 interface that is shared
-amongst other UNIX systems, in which case GRASS will look and behave pretty
-much the same as on other platforms. In the past, this required the
-user to have X11 from another source installed and running properly, but
+bundles with other traditonally-UNIX software packages. A <a
+ href="grasstep.sourceforge.net">Sourceforge project for porting GRASS to
+Quartz and GNUstep</a> has also been started, and is looking for programmers,
+if you have the skills and interest.<br>
+ <br>
+ The alternative approach is to stick with the X11 interface that is shared
+ amongst other UNIX systems, in which case GRASS will look and behave pretty
+ much the same as on other platforms. In the past, this required the
+ user to have X11 from another source installed and running properly, but
now (as of OS 10.3 "Panther") Apple includes X11 with the operating system,
combining XFree86 with a window manager that is integrated with the Aqua
graphics system. So if you have this version of the operating system,
@@ -79,49 +82,49 @@
way to run GRASS), it will use standard X11-based Tcl/Tk, and requires that
you have that installed separately. If you are still using OS 10.2
("Jaguar"), you can install X11 separately a number of ways (see below).<br>
- <br>
-In recent discussions on the GRASS development mailing list, it has been
-noted that things would be simpler if tcltkgrass, the GRASS menuing system,
-were modified so that it could be used without modification in the Aqua port
-of Tcl/Tk instead of requiring the UNIX version. So this may be changed
-in the near future, but in the meantime the issues above still apply. It
-has also been noted that the NVIZ visualization tool will continue to require
-the UNIX version of Tcl/Tk.<br>
-<br>
-These issues have contributed to the variety of versions you can install,
-whether you choose a binary installation or to compile from source. The
-prerequisites for each option vary slightly.<br>
-
+ <br>
+ In recent discussions on the GRASS development mailing list, it has been
+ noted that things would be simpler if tcltkgrass, the GRASS menuing system,
+ were modified so that it could be used without modification in the Aqua
+port of Tcl/Tk instead of requiring the UNIX version. So this may
+be changed in the near future, but in the meantime the issues above still
+apply. It has also been noted that the NVIZ visualization tool will
+continue to require the UNIX version of Tcl/Tk.<br>
+ <br>
+ These issues have contributed to the variety of versions you can install,
+ whether you choose a binary installation or to compile from source. The
+ prerequisites for each option vary slightly.<br>
+
<h1>Prerequisites</h1>
- All platforms require a number of external packages to make GRASS work, either
-at all, or to its full potential. Some of these are provided in a base
-Mac OS X system (the number of which has gone up over time), whereas others
-are easily available as downloaded binaries or source code. The requirements
-for compiling the software yourself are more complicated and are discussed
-first. If you are going to install pre-compiled binaries you can skip
-to the "Binaries" section of this document.<br>
- <br>
- <span DEFANGED_STYLE="text-decoration: underline;"><span
+ All platforms require a number of external packages to make GRASS work,
+either at all, or to its full potential. Some of these are provided
+in a base Mac OS X system (the number of which has gone up over time), whereas
+others are easily available as downloaded binaries or source code. The
+requirements for compiling the software yourself are more complicated and
+are discussed first. If you are going to install pre-compiled binaries
+you can skip to the "Binaries" section of this document.<br>
+ <br>
+ <span DEFANGED_STYLE="text-decoration: underline;"><span
DEFANGED_STYLE="font-weight: bold;">Requirements to compile GRASS:</span></span><br>
- <br>
- If you are going to do any compiling of software, you will need the development
-tools, available free from Apple. This package was called Development
-Tools for OS X versions 10.0-10.2, and "Xcode tools" when 10.3 ("Panther")
-was released. It is on a separate install CD in the Panther package
-and either on CD or available for download for earlier versions.<br>
- <br>
- The general prerequisites for all platforms are listed in the <a
+ <br>
+ If you are going to do any compiling of software, you will need the development
+ tools, available free from Apple. This package was called Development
+ Tools for OS X versions 10.0-10.2, and "Xcode tools" when 10.3 ("Panther")
+ was released. It is on a separate install CD in the Panther package
+ and either on CD or available for download for earlier versions.<br>
+ <br>
+ The general prerequisites for all platforms are listed in the <a
href="http://grass.ibiblio.org/grass5/source/REQUIREMENTS.html">GRASS requirements
-page</a>. Of these, all of the aboslutely required elements (e.g. the
-compiler/build system, and the zlib libraries) are provided by Apple.
-As discussed above, the X11 window system is provided by Apple as an optional
-install starting in OS X 10.3. For Mac OS X 10.2 (or earlier), you
+ page</a>. Of these, all of the aboslutely required elements (e.g.
+the compiler/build system, and the zlib libraries) are provided by Apple.
+ As discussed above, the X11 window system is provided by Apple as an optional
+ install starting in OS X 10.3. For Mac OS X 10.2 (or earlier), you
can install XFree86 using the <a href="http://fink.sourceforge.net">fink</a>
or <a href="http://darwinports.opendarwin.org">DarwinPorts</a> package manager
-systems, or compile it yourself from source.<br>
- <br>
- The package manager systems are an easy way to find, compile where necessary,
-and install ports of unix software on to a Mac OS X system. If you
+ systems, or compile it yourself from source.<br>
+ <br>
+ The package manager systems are an easy way to find, compile where necessary,
+ and install ports of unix software on to a Mac OS X system. If you
have used Cygwin on a Windows machine, or RedHat, Debian, etc. on a Linux
machine, you are probably already aware of their package managers.
On the Mac, you can choose from at least <a
@@ -133,76 +136,79 @@
satisfaction with DarwinPorts. You should read the web pages for those
two projects to learn about the differences between them, and how to install
and use them.<br>
- <br>
- <span DEFANGED_STYLE="font-weight: bold; text-decoration: underline;">Optional requirements
-</span><span DEFANGED_STYLE="text-decoration: underline;">(as listed in the </span><span
+ <br>
+ <span DEFANGED_STYLE="font-weight: bold; text-decoration: underline;">Optional
+requirements </span><span DEFANGED_STYLE="text-decoration: underline;">(as listed
+in the </span><span
DEFANGED_STYLE="font-weight: bold; text-decoration: underline;"> <a
href="../grass5/source/REQUIREMENTS.html">GRASS requirements page</a>)</span><span
DEFANGED_STYLE="font-weight: bold;"><span DEFANGED_STYLE="text-decoration: underline;">:</span><br>
- <br>
- </span>As of OS X version 10.3, Apple provides suitable versions of FreeType
-2 and OpenGL (if you have the Apple X11 installed).<br>
- <br>
- The rest of the optional requirements can be downloaded as source and compiled
-"manually", or installed with either of the package management systems (is
-this true of all the packages in DarwinPorts?). In fink, the packages
-you would need are: libtiff libtiff-shlibs libpng3 libpng3-shlibs libjpeg
-libjpeg-shlibs tcltk tcltk-dev tcltk-shlibs gd2 gd2-shlibs <span
+ <br>
+ </span>As of OS X version 10.3, Apple provides suitable versions of FreeType
+ 2 and OpenGL (if you have the Apple X11 installed).<br>
+ <br>
+ The rest of the optional requirements can be downloaded as source and
+compiled "manually", or installed with either of the package management
+systems (is this true of all the packages in DarwinPorts?). In fink,
+the packages you would need are: libtiff libtiff-shlibs libpng3 libpng3-shlibs
+libjpeg libjpeg-shlibs tcltk tcltk-dev tcltk-shlibs gd2 gd2-shlibs <span
DEFANGED_STYLE="font-style: italic;">gdal gdal-dev gdal-shlibs</span> (but see special
-note re: GDAL below) netpbm netpbm-shlibs postgresql postgresql73-dev unixodbc2
-unixodbc2-dev, and r-base (for the R language link to GRASS - note
-that this installs the X11/UNIX version of R, not the Aqua version).
-<br>
+ note re: GDAL below) netpbm netpbm-shlibs postgresql postgresql73-dev unixodbc2
+ unixodbc2-dev, and r-base (for the R language link to GRASS - note
+ that this installs the X11/UNIX version of R, not the Aqua version).
<br>
- <span DEFANGED_STYLE="font-weight: bold;">GDAL</span> deserves special mention, because
-the version that is generally available either as "released" source code,
-or as a fink package as of this writing is quite far behind the current development
-version, and it is the current versions of GDAL that are used in GRASS development.
-This tool and its use in GRASS is updated quite frequently, therefore if
-you don't have the most recent version of GDAL when you are trying to compile
-GRASS, there's a good chance that r.in.gdal compilation will fail, or that
-the tool will not work as expected. Therefore it is recommended that
-you install a relatively recent binary version of GDAL (e.g. <a
- href="http://wwwamb.bologna.enea.it/forgrass">http://wwwamb.bologna.enea.it/forgrass</a>
-)or compile from a recent version of the <a
+ <br>
+ <span DEFANGED_STYLE="font-weight: bold;">GDAL</span> deserves special mention,
+because the version that is generally available either as "released" source
+code, or as a fink package as of this writing is quite far behind the current
+development version, and it is the current versions of GDAL that are used
+in GRASS development. This tool and its use in GRASS is updated quite
+frequently, therefore if you don't have the most recent version of GDAL when
+you are trying to compile GRASS, there's a good chance that r.in.gdal compilation
+will fail, or that the tool will not work as expected. Therefore it
+is recommended that you install a relatively recent binary version of GDAL
+(e.g. <a href="http://wwwamb.bologna.enea.it/forgrass">http://wwwamb.bologna.enea.it/forgrass</a>
+ )or compile from a recent version of the <a
href="http://www.remotesensing.org/gdal/">sources available via anonymous
-CVS</a>. The r.in.gdal command is extremely useful for importing a
+ CVS</a>. The r.in.gdal command is extremely useful for importing a
wide variety of spatial data formats, so it is worthwhile spending the extra
effort to get this working if you will have any data import tasks.<br>
- <br>
-Tcl/Tk is required for the tcltkgrass menu/GUI system, and for the NVIZ visualization
-tool. At this time, GRASS distributed from the GRASS project sites
-does not work with the Tcl/Tk that is available for Apple's Aqua window environment,
-so you will need the UNIX version of Tcl/Tk to build GRASS from source. Hopefully,
-changes will soon be made that would allow tcltkgrass to use <a
- href="http://www.maths.mq.edu.au/%7Esteffen/tcltk/TclTkAqua/">Aqua Tcl/Tk</a>,
-but apparently making NVIZ work would be much more complicated (see mailing
-list traffic on this topic). You can install the tcltk package from
-fink, or it can be easily built from source (get source from <a
- href="http://sourceforge.net/project/showfiles.php?group_id=10894">the Tcl/Tk
-sourceforge project</a>. <br>
-<br>
-The <a href="http://www.remotesensing.org/proj/">PROJ library</a> also builds
-cleanly from source on the Mac platform.<br>
-<br>
-<br>
- <span DEFANGED_STYLE="text-decoration: underline;"><span
+ <br>
+ Tcl/Tk is required for the tcltkgrass menu/GUI system, and for the NVIZ
+visualization tool. At this time, GRASS distributed from the GRASS project
+sites does not work with the Tcl/Tk that is available for Apple's Aqua window
+environment, so you will need the UNIX version of Tcl/Tk to build GRASS from
+source. Hopefully, changes will soon be made that would allow tcltkgrass
+to use <a href="http://www.maths.mq.edu.au/%7Esteffen/tcltk/TclTkAqua/">Aqua
+Tcl/Tk</a>, but apparently making NVIZ work would be much more complicated
+(see mailing list traffic on this topic). You can install the tcltk
+package from fink, or it can be easily built from source (get source from
+<a href="http://sourceforge.net/project/showfiles.php?group_id=10894">the
+Tcl/Tk sourceforge project</a>. <br>
+ <br>
+ The <a href="http://www.remotesensing.org/proj/">PROJ library</a> also
+builds cleanly from source on the Mac platform.<br>
+ <br>
+ Some additional notes on configuring GRASS to compile on a Mac are now available
+<a href="macosx_grass50compile.html">here</a> - additional contributions welcome.<br>
+ <br>
+ <span DEFANGED_STYLE="text-decoration: underline;"><span
DEFANGED_STYLE="font-weight: bold;">Binary releases of GRASS for Mac OS X</span></span><br>
- <br>
-1) <u> Binary releases from the GRASS site</u> - There are binary packages
-available from the <a href="../download.html">GRASS downloads area</a> of
-this site. When these binary packages are constructed, reasonable efforts
-are made to package everything you need into a single download and install
-process. For example, the GDAL library discussed above is included.
-Some of the other GRASS modules that interface with other software packages
-will require separate installations for normal functionality. Such
-external packages include PostgreSQL (for the PostgreSQL database interface),
+ <br>
+ 1) <u> Binary releases from the GRASS site</u> - There are binary
+packages available from the <a href="../download.html">GRASS downloads area</a>
+of this site. When these binary packages are constructed, reasonable
+efforts are made to package everything you need into a single download and
+install process. For example, the GDAL library discussed above is
+included. Some of the other GRASS modules that interface with other
+software packages will require separate installations for normal functionality.
+Such external packages include PostgreSQL (for the PostgreSQL database interface),
Unix ODBC (for the ODBC database interface), and Tcl/Tk 8.x (for the graphical
-menu system and the NVIZ visualization tool). In addition, the Tcl/Tk
-is sometimes version-sensitive, therefore your installation version may need
-to match that used by the person that made the binaries. There are
-2 files to download, a large compressed archive with the required files (a
-.tar.gz file), and a script file that will manage the installation process.
+ menu system and the NVIZ visualization tool). In addition, the Tcl/Tk
+ is sometimes version-sensitive, therefore your installation version may
+need to match that used by the person that made the binaries. There
+are 2 files to download, a large compressed archive with the required files
+(a .tar.gz file), and a script file that will manage the installation process.
You need to download both files intact (i.e. don't let your browser
call on Stuffit Expander or any other decompression tool to process the .tar.gz
file), and then go to a Terminal window to run the install script. See
@@ -218,83 +224,88 @@
came to Macs from UNIX platforms, this is probably the most familiar route
for you. This option is also most likely to be the quickest to incorporate
the latest developments in the main GRASS code.<br>
- <br>
- Note that the package managers discussed in the above section on installing
-from source code can also be useful for installing these extra software packages.
-In some cases they will allow you to stick with "all-binary" installations,
-not requiring anything to be compiled - fink, for example, can do this using
-the apt-get command or using the "<a href="http://finkcommander.sf.net">Fink
-Commander</a>" graphical package management tool. Even if what you
-are after is not available in a binary format, the package managers provide
-an "intermediate" solution, in that as long as you have the development environment
-installed, they can take care of the downloading and compiling of the sources
-and the installation of the resulting binaries automatically. If you
-use Fink Commander, this is all managed within the Mac GUI, without having
-to navigate a UNIX shell prompt.<br>
- <br>
-2) <u>GRASS from Fink</u> - it should be noted that <a
+ <br>
+ Note that the package managers discussed in the above section on installing
+ from source code can also be useful for installing these extra software
+packages. In some cases they will allow you to stick with "all-binary"
+installations, not requiring anything to be compiled - fink, for example,
+can do this using the apt-get command or using the "<a
+ href="http://finkcommander.sf.net">Fink Commander</a>" graphical package
+management tool. Even if what you are after is not available in a binary
+format, the package managers provide an "intermediate" solution, in that
+as long as you have the development environment installed, they can take
+care of the downloading and compiling of the sources and the installation
+of the resulting binaries automatically. If you use Fink Commander,
+this is all managed within the Mac GUI, without having to navigate a UNIX
+shell prompt.<br>
+ <br>
+ 2) <u>GRASS from Fink</u> - it should be noted that <a
href="http://fink.sourceforge.net/pdb/package.php/grass">GRASS itself is
-available as a package, in the Fink system</a>, although as of this writing
-it is also still at version 5.0.2. It would be wonderful to get that
-updated, and to also have packages that install the development version 5.3
-and the experimental 5.7. But all of this requires scarce volunteer
-time.<br>
-<br>
-3) <u>Open OS X</u> - The <a href="http://openosx.com/grass/">Open
-OS X port of GRASS</a> is a binary release with extra functionality, but
+ available as a package, in the Fink system</a>, although as of this writing
+ it is also still at version 5.0.2. It would be wonderful to get that
+ updated, and to also have packages that install the development version
+5.3 and the experimental 5.7. But all of this requires scarce volunteer
+ time.<br>
+ <br>
+ 3) <u>Open OS X</u> - The <a href="http://openosx.com/grass/">Open
+ OS X port of GRASS</a> is a binary release with extra functionality, but
its maintenance and documentation is a parallel, separate activity (which
has contributed back some very useful fixes to the main GRASS project).
-As of this writing, it is still using version 5.0.2 of GRASS.<br>
-<br>
-4) <u>Lorenzo Moretti's "one stop" solution</u> - A relatively new
-solution has recently been made available from Lorenzo Moretti, at <a
+ As of this writing, it is still using version 5.0.2 of GRASS.<br>
+ <br>
+ 4) <u>Lorenzo Moretti's "one stop" solution</u> - A relatively new
+ solution has recently been made available from Lorenzo Moretti, at <a
href="http://wwwamb.bologna.enea.it/forgrass/">http://wwwamb.bologna.enea.it/forgrass/</a>
-which provides all of the software you need to run GRASS 5.3 and GRASS 5.7
-on any Mac with OS 10.2.8 or higher and Apple's X11 installed. I have
-not had a chance to try this yet, but it looks very promising. I gather
-he has adopted many conventions that will be more familiar to longtime Apple
-users (e.g. the programs are installed under /Applications instead of the
-usual /usr/local/grass5X), and it comes in the form of "one-click" Apple
+ which provides all of the software you need to run GRASS 5.3 and GRASS 5.7
+ on any Mac with OS 10.2.8 or higher and Apple's X11 installed. I have
+ not had a chance to try this yet, but it looks very promising. I gather
+ he has adopted many conventions that will be more familiar to longtime Apple
+ users (e.g. the programs are installed under /Applications instead of the
+ usual /usr/local/grass5X), and it comes in the form of "one-click" Apple
"packages" (.pkg files) so installation is simple. This is probably
a good option for those wanting to try GRASS that are wary about / inexperienced
with UNIX or other command-prompt driven operating systems.<br>
-<br>
-5) More? This list, and the impressions within it, reflect the
-initial author's personal experience and biases. <a
+ <br>
+ 5) More? This list, and the impressions within it, reflect
+the initial author's personal experience and biases. <a
href="mailto:weblist at grass.itc.it">Feedback and additional information is
-highly encouraged</a>.<br>
-<br>
- <b>This is still an initial draft document - the rest of this page is "leftovers"...<br>
-<br>
- is still</b><b><a href="GRASS.MacOSX.binnote.html"> Other info to incorporate</a><br>
- </b>
-<p><b><br>
- Download source code (to compile GRASS from scratch on Windows):</b> </p>
-
+ highly encouraged</a>.<br>
+ <br>
+ <b>This is still an initial draft document - the rest of this page is
+"leftovers"...<br>
+ <br>
+ is still</b><b><a href="GRASS.MacOSX.binnote.html"> Other info to
+incorporate</a></b> and <a href="macosx_buildnotes.html">even more</a>.<br>
+<p><b> Download source code (to compile GRASS from scratch on Windows):</b>
+</p>
+
<ul>
- <li>Get the latest <a href="../download.html">GRASS 5 sources.</a></li>
- <li> <a href="macosx_grass50compile.html">Instructions on how to compile</a>
-GRASS 5.0 on Mac OS X.</li>
-
+ <li>Get the latest <a href="../download.html">GRASS 5 sources.</a></li>
+ <li> <a href="macosx_grass50compile.html">Instructions on how to compile</a>
+ GRASS 5.0 on Mac OS X.</li>
+
</ul>
-
-<hr width="100%" noshade="noshade" size="3">
-<h3>FAQ (related to XXXX)</h3>
- <br>
- <br>
-
+
+<hr width="100%" noshade="noshade" size="3">
+<h3>A FAQ section would be good here - Suggestions for FAQ's welcome.<br>
+ </h3>
+ <br>
+ <br>
+
<ul>
-
+
</ul>
- <!-- FOOTER -->
-<hr>
+ <!-- FOOTER -->
+<hr>
<div align="right">© 2003 GRASS Development Team<br>
- <a href="mailto:weblist at grass.itc.it">Comments</a> about this page | <a
+ <a href="mailto:weblist at grass.itc.it">Comments</a> about this page | <a
href="../faq/index.html">FAQ</a> | <a href="../download.html">Download</a>
-| <a href="../support.html">Support</a> | <a href="../gdp/index.html">Docs</a>
-| <a href="../grassdevel.html">Programming</a> | Back <a
+ | <a href="../support.html">Support</a> | <a href="../gdp/index.html">Docs</a>
+ | <a href="../grassdevel.html">Programming</a> | Back <a
href="../index.html">HOME</a><br>
- <i>Last change: $Date$ </i></div>
+ <i>Last change: $Date$ </i></div>
+ <br>
+ <br>
<br>
</body>
</html>
More information about the grass-web
mailing list