Paul Kelly wrote: > Although maybe > long-term we could move away from using the gdal-config command in the > configure script to get away from problems like this. I think everything > its used for should probably be able to be achieved without it.
I wouldn't be so sure. GDAL can require a *lot* of other libraries (by its nature, it's a front-end to various raster data libraries), some of which might be in non-obvious locations, and may have substantial dependencies of their own. AFAICT, the only alternative is to provide a --with-gdal-ldflags= switch and require the user to specify exactly which flags are required to link against GDAL. Implementing such a switch would be straightforward; getting the average user (or developer) to figure out what value to provide would be rather less straightforward. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
