You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I have researched, it is currently not possible to reliably determine the default gdalplugins lib path for out-of-source drivers/plugins (due to "lib" vs "lib64" directory names).
Could gdal-config be extended with a --plugindir option to print it out ? (as there doesn't seem to be a standard option to print this out with pkg-config)
Furthermore, there seems to be some inconsistencies in the generated gdal.pc file (note the invalid but unused value for $libdir)
From what I have researched, it is currently not possible to reliably determine the default gdalplugins lib path for out-of-source drivers/plugins (due to "lib" vs "lib64" directory names).
Could gdal-config be extended with a --plugindir option to print it out ? (as there doesn't seem to be a standard option to print this out with pkg-config)
Furthermore, there seems to be some inconsistencies in the generated gdal.pc file (note the invalid but unused value for $libdir)
The text was updated successfully, but these errors were encountered: