Hi again Hamish, Thanks for the Makefile suggestions, I will try Makefile.gipe, it is closer to actual method.
I have updated the wiki, but it is still not reflecting all new things in GIPE. I have been checking up gem a year or so ago, but I found out more useful to concentrate on making GIPE modules more robust. Still I am full in making it all work. Any suggestions from people about how to manage such thing is more than welcome. Yann 2008/6/2 Hamish <[EMAIL PROTECTED]>: > We should cc/move this thread to grass-dev for other eyes... > > > Hamish: >> > Better just to have a gipe Makefile which includes all >> > gipe modules and nothing else. > > Yann Chemin wrote: >> I am OK to do so, but how can it be run in imagery/ or in >> raster/, since there is already a Makefile in those places? > > I can think of two ways: > 1) keep gipe i.* and r.* modules in their own gipe/ dir in the grass source > tree, then run "make" in the gipe/ dir to make them all. > > 2) If you feel you must mix the gipe modules into grass raster/ and imagery/ > source code dirs, add a new file called Makefile.gipe with just gipe modules, > then "make -f Makefile.gipe" to use the alternate Makefile name. > > > Did you get anywhere with using GEM? I am not sure how that has it organized > but I assume it has worked out some way. As Gipe grows it becomes more and > more a addon enhancement package rather than just some nice collection of > modules. > > > regards, > Hamish > > > > > > > -- Yann Chemin International Rice Research Institute Office: http://www.irri.org/gis Perso: http://www.freewebs.com/ychemin _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
