Le mercredi 28 mai 2014 21:27:54, Gordon Farquharson a écrit : > Thanks for the quick answer. Would the approach of turning GDAL utility > code into libraries be as simple as putting the code into .h and .cpp > files, or would you want to do it in a more globally organized way, e.g.., > to develop a sensible class hierarchy and a consistent naming scheme?
Everything can be considered. Proposals welcome. At the minimum, work should be done to remove global variables, avoid exit() calls, etc... so that it can be used as a proper library function. And it would be good if that library'fication of utilities should allow to pass dataset objects instead of strings for example. > > Gordon > > > On Wed, May 28, 2014 at 12:18 PM, Even Rouault > <even.roua...@mines-paris.org > > > wrote: > > > > Le mercredi 28 mai 2014 21:03:40, Gordon Farquharson a écrit : > > > The VRTBuilder class in the gdalbuildvrt utility source code is very > > > useful. Is there any intention to make it part of the GDAL API? > > > > > > Gordon > > > > Gordon, > > > > the idea of turning the code of GDAL utilities as library code reusable > > by user code has floated around. It probably waits for contributions > > and/or funding. In the mean time, you can "import" the code into your > > code. > > > > Even > > > > -- > > Geospatial professional services > > http://even.rouault.free.fr/services.html -- Geospatial professional services http://even.rouault.free.fr/services.html _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
