Markus Neteler
74f847c0f9
wording
|
12 年 前 | |
|---|---|---|
| db | 12 年 前 | |
| debian | 13 年 前 | |
| demolocation | 12 年 前 | |
| display | 12 年 前 | |
| doc | 12 年 前 | |
| general | 12 年 前 | |
| gui | 12 年 前 | |
| imagery | 12 年 前 | |
| include | 12 年 前 | |
| lib | 12 年 前 | |
| locale | 12 年 前 | |
| macosx | 12 年 前 | |
| man | 12 年 前 | |
| misc | 12 年 前 | |
| mswindows | 12 年 前 | |
| ps | 13 年 前 | |
| raster | 12 年 前 | |
| raster3d | 12 年 前 | |
| rfc | 13 年 前 | |
| rpm | 15 年 前 | |
| scripts | 12 年 前 | |
| temporal | 12 年 前 | |
| testsuite | 17 年 前 | |
| tools | 12 年 前 | |
| vector | 12 年 前 | |
| visualization | 12 年 前 | |
| AUTHORS | 13 年 前 | |
| CHANGES | 17 年 前 | |
| COPYING | 14 年 前 | |
| GPL.TXT | 17 年 前 | |
| INSTALL | 15 年 前 | |
| Makefile | 13 年 前 | |
| README | 15 年 前 | |
| REQUIREMENTS.html | 12 年 前 | |
| SUBMITTING | 12 年 前 | |
| SUBMITTING_DOCS | 12 年 前 | |
| SUBMITTING_PYTHON | 12 年 前 | |
| SUBMITTING_WXGUI | 12 年 前 | |
| TODO | 17 年 前 | |
| aclocal.m4 | 12 年 前 | |
| binaryInstall.src | 12 年 前 | |
| config.guess | 12 年 前 | |
| config.sub | 12 年 前 | |
| configure | 12 年 前 | |
| configure.in | 12 年 前 | |
| contributors.csv | 13 年 前 | |
| contributors_extra.csv | 13 年 前 | |
| grass.pc.in | 17 年 前 | |
| grasslib.dox | 13 年 前 | |
| install-sh | 15 年 前 | |
| translators.csv | 12 年 前 |
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/programming7/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/programming7/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/programming7/
##########################################################
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/programming7/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/programming7/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/programming7/