Re: [gdal-dev] limiting drivers that get registered

On 27/03/18 22:00, Even Rouault wrote: > Ah that was apparently your actual need rather than limiting the number of > drivers per-se. Do you have profiled where time was lost if you find opening > too slow ? The identification logic of drivers is supposed to operate fast > (extension based, or

Re: [gdal-dev] limiting drivers that get registered

On mardi 27 mars 2018 21:51:46 CEST Ben Elliston wrote: > On 27/03/18 21:49, Even Rouault wrote: > > Hum why would you need to call GDALAllRegister() if you already manually > > registered some of them ? > > Because reordering the driver list by placing commonly used drivers at > the head of the

Re: [gdal-dev] limiting drivers that get registered

On 27/03/18 21:49, Even Rouault wrote: > Hum why would you need to call GDALAllRegister() if you already manually > registered some of them ? Because reordering the driver list by placing commonly used drivers at the head of the list makes a significant difference in the time taken to open

Re: [gdal-dev] limiting drivers that get registered

On mardi 27 mars 2018 21:09:41 CEST Ben Elliston wrote: > Hi Even > > On 08/03/18 23:34, Even Rouault wrote: > > If you use GDAL as a library from your own code (C/C++), you can also > > directly call the GDALRegister_() / OGRRegister() functions you > > are interested in, instead of

Re: [gdal-dev] limiting drivers that get registered

Hi Even On 08/03/18 23:34, Even Rouault wrote: > If you use GDAL as a library from your own code (C/C++), you can also > directly call the GDALRegister_() / OGRRegister() functions you > are interested in, instead of GDALAllRegister() This is ideal, as it allows a handful of drivers to

Re: [gdal-dev] limiting drivers that get registered

On 09/03/18 10:43, br...@frogmouth.net wrote: > I think you should feel free to make general improvements to the autotools > setup  Is this my past coming back to haunt me? :-) Ben ___ gdal-dev mailing list gdal-dev@lists.osgeo.org

Re: [gdal-dev] limiting drivers that get registered

I think you should feel free to make general improvements to the autotools setup  Brad -Original Message- From: gdal-dev <gdal-dev-boun...@lists.osgeo.org> On Behalf Of Ben Elliston Sent: Thursday, 8 March 2018 11:24 PM To: gdal-dev@lists.osgeo.org Subject: [gdal-dev] limiting d

Re: [gdal-dev] limiting drivers that get registered

I use bazel for building, so the build info isn't useful. You'll have to hack the makefiles a bit. I also tried to stop things from registering... find . -name \*.cpp | egrep -v 'autotest|swig|apps|fuzzers|gdaldrivermanager.cpp|ogrregisterall.cpp|gdalallregister.cpp' | xargs egrep

Re: [gdal-dev] limiting drivers that get registered

Am Do, 8.03.2018, 17:47 schrieb 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. > Share, share, share :)

Re: [gdal-dev] limiting drivers that get registered

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

Re: [gdal-dev] limiting drivers that get registered

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 : > Is it possible to limit the number of drivers compiled into

Re: [gdal-dev] limiting drivers that get registered

Ben, > Is it possible to limit the number of drivers compiled into GDAL (I am > guessing not)? You have some knobs with the various ./configure or nmake.opt switch, but yes generally drivers that don't require external dependencies will always be compiled in. Editing manually the makefiles can

[gdal-dev] limiting drivers that get registered

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