<div dir="ltr">I was just writing again... answering to my (stupid) question by myself.<br>I was getting lost between GDAL and GRASS! :-)<br>Thanks anyway.<br><br><div class="gmail_quote">2008/8/14 Glynn Clements <span dir="ltr"><<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
G. Allegri wrote:<br>
<br>
> perfect. I was used to build grass, then build gdal with grass, and<br>
> then rebuild grass. This time I'll follow your suggestion:<br>
> I've just built gdal 1.5.2 (without grass) and grass (--with-gdal) ,<br>
> and now I will compile gdal-grass plugin <a href="http://1.4.2." target="_blank">1.4.2.</a><br>
><br>
> Last question (I'm sorry for my ignorance!): why grass configure asks<br>
> for --with-gdal? Does this option prepare grass to use the gdal-grass<br>
> plugin?<br>
<br>
</div>GRASS needs GDAL.<br>
<br>
The --with-gdal switch allows the path to the gdal-config script to be<br>
passed as an argument, in case it isn't in the path, or in case you<br>
want to use a version other than the one which comes first in the<br>
path. You can't use --without-gdal or --with-gdal=no; GDAL is<br>
non-optional.<br>
<br>
However, GRASS doesn't require that GDAL is built with GRASS support,<br>
or the GDAL-GRASS plugin.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="Wj3C7c">Glynn Clements <<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>><br>
</div></div></blockquote></div><br></div>