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

Update 2020: this page is mildly outdated. The addon manual pages are now generated on grasslxd server (container on osgeo7). For details, see

AddOns XML file

GRASS AddOns metadata XML file can be created by 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.


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

There is also available script called which compiles GRASS AddOns modules for GRASS 6 and GRASS 7 and creates XML metadata file. This script simply calls and When running the script the main log file is stored in ~/grass<version>/addons/log/ALL.log and each modules log in ~/.grass<version>/addons/log/<module>.log. Beside that the script also prints basic information about progress to standard output

At revision 49265.
AddOns '/home/landa/.grass7/addons'...
Compiling d.mon2... SUCCESS
Compiling SUCCESS
Compiling v.unpack... SUCCESS
AddOns '/home/landa/.grass6/addons'...
Compiling d.barb... SUCCESS
Compiling d.edit.rast... SUCCESS
Compiling v.what.rast.buffer... SUCCESS
Creating XML file '/home/landa/.grass7/addons/modules.xml'...
Parsing <d.mon2>...  SUCCESS
Parsing <>...  SUCCESS
Parsing <v.unpack>...  SUCCESS
Creating XML file '/home/landa/.grass6/addons/modules.xml'...
Parsing <d.barb>...  FAILED
Parsing <d.edit.rast>...  SUCCESS
Parsing <v.what.rast.buffer>...  SUCCESS

Automatically created XML files are available from

Compile AddOns on MS Windows

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

If you would like to try to build them yourself you must ensure that the osgeo4w and GRASS software is located in paths without spaces in them. The Make system we use can't deal with that, and it is beyond our control to fix.

The GRASS AddOns binaries are downloaded in winGRASS by default from, eg. for GRASS 7 it's The GRASS AddOns are compiled on that server by script available from SVN.

Last modified 2 years ago Last modified on Jan 1, 2022, 3:29:40 AM
Note: See TracWiki for help on using the wiki.