This page collects information about ​GRASS AddOns management from developer point of view.

AddOns XML file

GRASS AddOns metadata XML file can be created by build-xml.py​ Python script available from SVN. It's creating XML file modules.xml in ~/.grass6/addons for GRASS 6 and in ~/.grass7/addons for GRASS 7.

Example:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task SYSTEM "grass-addons.dtd">
<modules version=7.0.svn>
    <task name="d.mon2">
        <description>Starts a graphics display monitor which can be controlled from the command line.</description>
        <keywords>display,CLI</keywords>
    </task>
    <task name="i.points.auto">
        <description>Generate ground control points for image group to be rectified.</description>
        <keywords>imagery,ground control points</keywords>
    </task>
...
    <task name="v.unpack">
        <description>Unpacks a vector map packed with r.pack.</description>
        <keywords>vector,import,copying</keywords>
    </task>
</modules>

Compile AddOns on MS Windows

Background: g.extension in winGRASS is not trying to compile given AddOn as on GNU/Linux, it just downloads pre-compiled binaries from the server.

The GRASS AddOns binaries are downloaded in winGRASS by default from ​http://wingrass.fsv.cvut.cz, eg. for GRASS 7 it's ​http://wingrass.fsv.cvut.cz/grass70/addons. The GRASS AddOns are compiled on that server by script compile.sh​ available from SVN.