On Thu, Jun 5, 2008 at 3:20 PM, <[EMAIL PROTECTED]> wrote: [ great stuff skipped] ... > Since Windows users cannot build binaries by themselves, it would be good to > build and distribute also the GRASS AddOns. I'm not sure now how to > distribute them (even if I've got some WIP ideas), but I surely need to > create a simple procedure to build and install them all in a separated > directory, with a build procedure indipendent from the GRASS build procedure > itself.
I feel that the *build* procedure is pretty dependent on the GRASS build procedure. But that's no problem: > Since now I built addons putting the sources in the GRASS source tree and > adding the addons to build in the general make files (for example adding > r.horizon into the list of building modules in /raster/Makefile). But if I > put the addons sources outside the main GRASS source tree, I would need to > change the paths from relative to absolute in each module, and then create a > Makefile for each addon module... too much work for a frequent task! Any > suggestions? That's not needed. You can compile with: cd grass-addons/raster/r.sun_horizon/ make MODULE_TOPDIR=$HOME/grass64/ This will compile it into the main GRASS code tree. Markus _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
