[GRASS-user] AddOn or Script when compiling GRASS from source
JRadinger at gmx.at
Wed Oct 12 16:32:17 EDT 2011
I used the modules-folder in the library already on OS X for GRASS 6.5
and 6.4. I can't remember but are
this folder structure automatically installed when installing GRASS?
Because after compiling and installing
GRASS 7 SVN no such folders were created. Maybe I can just copy the
folder structure from GRASS 6.5 and
rename it with the new version.
Anyway I am interested in compiling and installing and AddOn or Script
with the source code. This is on
the one hand for me to learn how to do such things on different
plattforms (and create my own binaries).
On the other hand with when an AddOn or Script is compiled with a
makefile also the html-help files
are generated which I find also really useful.
So maybe someone can tell me what is the difference between an AddOn and
a Script? What was the
main purpose to include both in the source? Where does my little module
fit better and is there
any difference in working with it as AddOn or Script?
Am 11.10.2011 16:17, schrieb William Kyngesburye:
> On OS X there are defined addon folders so you don't have to put anything in the application or some random path.
> where [grassver] is the major.minor grass version.
> This folder has a standard complement of bin/, docs/, etc/ and lib/. bin/ doesn't care whether it's a script or compiled module, they all go here (unlike the main app that separates bin and scripts).
> The startup will add anything in docs/html to an addon help page accessible from the Apple Help app (separate entry from the GRASS app help there).
> The startup also creates an extension menu for the GUI.
> This is all a part of the Mac build, and I don't know what, if anything, the Windows build does about this.
> On Oct 11, 2011, at 7:30 AM, Johannes Radinger wrote:
>> first of all I want to thank you for helping me in the past to learn
>> how to compile GRASS. Now I am already able to compile GRASS GIS from SVN source on my Mac (and hopefully soon on Windows as well) including also AddOns like r.stream etc.
>> The main purpose for learning this was that I also wrote a small python script/addon about fish dispersal which I want to use in future. In the past I put my python file into the modules/bin folder in my library. Then I was able to call it just with module.py.
>> As I now also wrote a html description I wanted to build this script/addon with my source code.
>> Here comes my question: What is now what I have? Is this a raster-addon or a script? What is the difference or is it just a matter of taste? I can put it into the script or the raster folder of my source (and modify the makefile accordingly). But where should it go?
>> What I want in the end is just to call the it via the grass command-console in the gui and it should then contain the html-help-file.
>> I'll also provide that addon/script to you as soon as it is working without any problems. Additionally I'll probably provide a sample dataset resp. a "how to use" file.
>> Thank you very much!
>> NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
>> Jetzt informieren: http://www.gmx.net/de/go/freephone
>> grass-user mailing list
>> grass-user at lists.osgeo.org
> William Kyngesburye<kyngchaos*at*kyngchaos*dot*com>
> "Time is an illusion - lunchtime doubly so."
> - Ford Prefect
More information about the grass-user