Developing custom GRASS programs - Revision history

Dgroulx: /* The C language */

2010-01-04T21:45:59Z

The C language

2010-01-04T21:41:54Z

Get the GRASS source

2010-01-04T21:41:00Z

Get the GRASS source

2010-01-04T21:39:55Z

2009-10-19T16:30:31Z

The makefile

2009-10-18T03:12:20Z

The C language

2009-10-16T20:27:26Z

Allocating Buffers

2009-10-16T17:56:18Z

Line 106-126 - Opening a raster map

2009-10-16T17:14:01Z

The C language

2009-10-16T17:10:54Z

@@ Line 419: / Line 419: @@
 Unlike the R and MATLAB languages, C is not designed to be user friendly, and really enjoys allowing you to blow your own
 foot off. If you are serious about writing your own custom GRASS programs, a basic understanding of the C language will
-save you hours of headaches ltter on.  The [http://www.faqs.org/docs/learnc/index.html Learning GNU C] tutorial is a
+save you hours of headaches later on.  The [http://www.faqs.org/docs/learnc/index.html Learning GNU C] tutorial is a
 decent place to start learning.

@@ Line 28: / Line 28: @@
 compile GRASS.  Unfortunately, GRASS has a long list of dependencies, and building can be rather difficult.
-An explanation of building software and all it's dependancies is beyond the scope of this tutorial.  However, learning to build the software yourself can be a useful skill.  For example, GRASS can support NetCDF, a format we intend to use more in the future.  However, most pre-built GRASS installations do not use this functionality.  By building GRASS yourself, you can have access to useful tools before they become mainstream.
+An explanation of building software and all it's dependancies is beyond the scope of this tutorial.  However, learning to build the software yourself can be a useful skill.  For example, GRASS can support NetCDF, a format we intend to use more in the future.  However, most pre-built GRASS installations do not use this functionality.  By building GRASS yourself, you gain access to useful tools before they become mainstream.
 ===Examining the GRASS source===

@@ Line 24: / Line 24: @@
-Next, getting the GRASS source.  To download the GRASS source, go to http://grass.itc.it/download/index.php.  It is best to download
+If you do not have these files, or still want to download GRASS directly from source to have access to the example code, keep reading.  To download the GRASS source, go to http://grass.itc.it/download/index.php.  It is best to download
 the RC code, as svn code may have issues compiling.  If you did not find the necessary .h and .dylib files, it will be necessary to
 compile GRASS.  Unfortunately, GRASS has a long list of dependencies, and building can be rather difficult.

@@ Line 17: / Line 17: @@
 # Open a terminal window
 # cd to the folder containing your GRASS executable
-# $> '''ls <GRASS app name>/Contents/MacOS/include/grass'''
+# $> '''ls <GRASS app path>/Contents/MacOS/include/grass'''
 # If you see several files ending in .h, one of which is gis.h, then you have the GRASS headers.
-# $> '''ls <GRASS app name>/Contents/MacOS/lib'''
+# $> '''ls <GRASS app path>/Contents/MacOS/lib'''
 # You should see a long list of files ending in .dylib.  Make sure that one of them is libgrass_gis.dylib.
 # If your GRASS install had both the .h and .dylib files, then you already have the necessary files and do not need to download the source.

← Older revision		Revision as of 16:30, 19 October 2009
Line 427:		Line 427:

	====The makefile====		====The makefile====
		+	For more information on customizing your own makefiles, see [http://www.gnu.org/software/make/manual/make.html GNU make]

@@ Line 330: / Line 330: @@
-====Allocating Buffers====
+====Line 130-140 -Allocating Buffers====
 <code>
      /* Allocate input buffer */

@@ Line 327: / Line 327: @@
      if (G_get_cellhd(name, mapset, &cellhd) < 0)
      G_fatal_error(_("Unable to read file header of <%s>"), name);
 </code>

← Older revision		Revision as of 17:14, 16 October 2009
Line 397:		Line 397:
	save you hours of headaches latter on. The [http://www.faqs.org/docs/learnc/index.html Learning GNU C] tutorial is a		save you hours of headaches latter on. The [http://www.faqs.org/docs/learnc/index.html Learning GNU C] tutorial is a
	decent place to start learning.		decent place to start learning.
		+
		+
		+	===GRASS Program Project Template===
		+
		+	====The code====
		+
		+	====The makefile====

@@ Line 297: / Line 297: @@
 Note the use of the atoi() and atof() functions. GRASS stores the option result as an array of characters, which is different than how C
 represents a number. These two functions convert the text version of the numbers into the actual representation.
 ====Line 156-176 - Process Data====
@@ Line 333: / Line 364: @@
   important to process ALL raster types, as this greatly increases the usability of
   your software.
 ====Line 183-198 - Memory cleanup and exiting====