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_XXXX() / OGRRegisterXXXX() functions you > > are interested in, instead of GDALAllRegister() > > This is ideal, as it allows a handful of drivers to be registered first, > and then GDALAllRegister() to be called to register everything else down > the line
Hum why would you need to call GDALAllRegister() if you already manually registered some of them ? > . Unfortunately, it is impossible to know which drivers are > present until you call an undefined function in the GDAL shared library. > For example, GDALRegister_HDF4() is not defined if the HDF4 library > isn't found at configure time. > > Is there any way to know which drivers are available at runtime? Well, call GDALAllRegister() and then query GDALGetDriverByName(driver_name). You can unregister a driver with GDALDeregisterDriver() Even -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev