<!DOCTYPE html><html><head><title></title><style type="text/css">#qt p.qt-MsoNormal{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:0in;font-size:11pt;font-family:"Calibri", sans-serif;}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style="font-family:Arial;">Hi Jesse,<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;"><a href="https://gdal.org/api/gdaldriver_cpp.html#_CPPv4N17GDALDriverManager15AutoLoadDriversEv">https://gdal.org/api/gdaldriver_cpp.html#_CPPv4N17GDALDriverManager15AutoLoadDriversEv</a> should answer your question.<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">Laurentiu<br></div><div style="font-family:Arial;"><br></div><div>On Mon, Dec 11, 2023, at 18:11, Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] via gdal-dev wrote:<br></div><blockquote type="cite" id="qt" style="overflow-wrap:break-word;"><div class="qt-WordSection1"><p class="qt-MsoNormal">Hi,<br></p><p class="qt-MsoNormal"> <br></p><p class="qt-MsoNormal">I know drivers can be built as plugins, but can they be detected / used by GDAL if they are not registered via gdal_frmts.h? It doesn’t seem so. Is this a C++ ABI restriction? We’d like to provide members of our team an internal and
custom gdal driver implementation without each of them needing a special GDAL build.<br></p><p class="qt-MsoNormal"> <br></p><p class="qt-MsoNormal">Best,<br></p><p class="qt-MsoNormal">Jesse<br></p></div><div>_______________________________________________<br></div><div>gdal-dev mailing list<br></div><div><a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br></div><div><a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br></div><div><br></div></blockquote><div style="font-family:Arial;"><br></div></body></html>