Hi, >maybe it would be better, or at least to make note like "this package is required for GRASS compilation", etc.
Ok. I'll do that later, before to release the final version. What about GEOS, GSL and Expat? Actually, GRASS uses none of them, but GDAL uses GEOS, I'm not sure if it uses GSL (even if I think not) and it would use Expat ...if I could be able to enable that support in GDAL :-) So, summarizing, for the GRASS guide only, should I remove GSL, Expat and GEOS or leave only GEOS? Marco -----Messaggio originale----- Da: Martin Landa [mailto:[EMAIL PROTECTED] Inviato: sabato 1 marzo 2008 14.44 A: Marco Pasetti Cc: GRASS Developer Mailing List Oggetto: Re: R: [GRASS-dev] New Binary Package Project for winGRASS Hi, 2008/3/1, Marco Pasetti <[EMAIL PROTECTED]>: > Related to this (the guide): what do you think about keeping GRASS + > Quantum GIS building guide together? Actually some things (like > expat, geos and gsl) are not needed by GRASS, but they are for QGIS. > Should I prepare two different documents, one for GRASS only and one > for both GRASS and QGIS maybe it would be better, or at least to make note like "this package is required for GRASS compilation", etc. Martin -- Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa * _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
