[gdal-dev] limiting drivers that get registered

[Kurt Schwehr]

I get a little more aggressive compared to what others suggested by
commenting out register calls in gdalallregister.cpp and ogrregisterall.cpp
and removing the code for the drivers.

There are gotchyas lurking, but it definitely works.

e.g.
Enable HDF5, but block BAG
Enable EHDR & ENVI, but leave out the rest of the raw drivers

On Thu, Mar 8, 2018 at 4:36 AM, Tobias Wendorff <
tobias.wendorff at tu-dortmund.de> wrote:

> I have created a config for minimal raster and vector.
>
> I can uploaded later when I am at home.
>
> --
> Von einem iPhone gesendet und wird daher Fehler enthalten…
>
> Am 08.03.2018 um 13:23 schrieb Ben Elliston <ben.elliston at anu.edu.au>:
>
> > Is it possible to limit the number of drivers compiled into GDAL (I am
> > guessing not)?  Alternatively, would a patch be welcome to read a
> > confguration file to limit which drivers are registered at
> initialisation?
> >
> > Cheers,
> > Ben
> > _______________________________________________
> > gdal-dev mailing list
> > gdal-dev at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/gdal-dev
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>



-- 
--
http://schwehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20180308/ae2ae909/attachment.html>