[GRASS-user] grass6.4 develbrunch revision 32726: undefined
reference to `G_no_gisinit'
G. Allegri
giohappy at gmail.com
Thu Aug 14 10:00:09 EDT 2008
perfect. I was used to build grass, then build gdal with grass, and
then rebuild grass. This time I'll follow your suggestion:
I've just built gdal 1.5.2 (without grass) and grass (--with-gdal) ,
and now I will compile gdal-grass plugin 1.4.2.
Last question (I'm sorry for my ignorance!): why grass configure asks
for --with-gdal? Does this option prepare grass to use the gdal-grass
plugin?
2008/8/14 Glynn Clements <glynn at gclements.plus.com>:
>
> G. Allegri wrote:
>
>> I didn't know that such a backward check on library version could be
>> done... my ignorance :-)
>>
>> So, you suggest to avoid gdal --with-grass. What if I need to access
>> grass datas from outside grass, like with gdal/ogr utilities?
>
> Use the GDAL-GRASS plug-in. Then, you only need to re-compile the
> plug-in whenever you update GRASS.
>
> Alternatively:
>
> Build and install GRASS 6.3. Build GDAL --with-grass, and install it.
> Use this for QGIS, GDAL utilities, etc.
>
> Build GDAL again --without-grass and install it somewhere it won't
> normally be found (i.e. not in /usr or /usr/local).
>
> If you want to use an updated version of GRASS, build it against the
> GRASS-less GDAL and run it in place.
>
> Even without this specific issue, building GDAL --with-grass is
> problematic as GRASS depends quite heavily upon GDAL, so having a
> version of GDAL which depends upon GRASS creates a circular
> dependency.
>
> --
> Glynn Clements <glynn at gclements.plus.com>
>
More information about the grass-user
mailing list