https://github.com/osgeo/grass-legacy
Legacy code repository of GRASS GIS versions 3.2, 4.x, 5.x, 6.x (1987-2016)
https://github.com/osgeo/grass-legacy
grass-gis legacy-code
Last synced: 10 months ago
JSON representation
Legacy code repository of GRASS GIS versions 3.2, 4.x, 5.x, 6.x (1987-2016)
- Host: GitHub
- URL: https://github.com/osgeo/grass-legacy
- Owner: OSGeo
- License: other
- Created: 2019-05-17T16:33:51.000Z (almost 7 years ago)
- Default Branch: develbranch_6
- Last Pushed: 2019-05-19T17:29:37.000Z (almost 7 years ago)
- Last Synced: 2025-06-21T03:33:20.938Z (10 months ago)
- Topics: grass-gis, legacy-code
- Language: C
- Homepage: https://grass.osgeo.org
- Size: 234 MB
- Stars: 8
- Watchers: 9
- Forks: 6
- Open Issues: 0
-
Metadata Files:
- Readme: README
- Changelog: CHANGES
- License: COPYING
Awesome Lists containing this project
README
GRASS Development Subversion repository
##########################################################
How to get write access here?
Write access is only granted to developers who agree to abide by
RFC2 - Legal aspects of code contributions
http://grass.osgeo.org/programming6/rfc/rfc2_psc.html
and the code submission guidelines (file SUBMITTING in this
directory).
This needs to be communicated to a GRASS developer. S/he will
then possibly propose you to the GRASS Project Steering committee
after a period of evaluation. For details, see
http://grass.osgeo.org/programming6/rfc/
Once write access is granted, you, the new developer need to
obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid
If you already have an "osgeo_id" but forgot it, search for it at
Search at http://www.osgeo.org/cgi-bin/ldap_web_search.py
##########################################################
How to compile GRASS:
See INSTALL file.
Yes, you should really read INSTALL.
##########################################################################
How to generate the 'Programmer's Manual':
This needs doxygen (http://www.doxygen.org) and optionally
Graphviz dot (http://www.research.att.com/sw/tools/graphviz/).
To build the GRASS programmer's documentation, run
make htmldocs
or to generate documentation as single html file (recommended for simple reading)
make htmldocs-single
here. This takes quite some time. The result is in lib/html/index.html
which refers to further document repositories in
lib/vector/html/index.html
lib/db/html/index.html
lib/gis/html/index.html
The master file is: ./grassrefman.dox where all sub-documents have to
be linked into.
To generate the documents in PDF format, run
make pdfdocs
An online version is available at:
http://grass.osgeo.org/programming6/