Hi Andre,
The solution you proposed is something special. In common case this is
library responsible to solve such situation.
Following you logic, the gdal have to deny using global environment
variable GDAL_DRIVER_PATH and require that each developer set this
variable manually in code or inpu
Am 15.05.2014 12:07, schrieb Dmitriy Baryshnikov:
I found out that another program used the gdal 1.8 was installed on that
PC. And this program create env variable GDAL_DRIVER_PATH which pointed
on some non standard driver linked with gdal 1.8
I think some version checking needed or something
Selon Dmitriy Baryshnikov :
> Hi,
>
> Yesterday I faced interesting problem on Win7 64 bit.
> My program uses last gdal version 1.12. During start the error message
> popuped in dialog that gdal v. 1.8 was not find and application closed.
> I checked with dependency walker what were was no gdal 1.
Hi,
Yesterday I faced interesting problem on Win7 64 bit.
My program uses last gdal version 1.12. During start the error message
popuped in dialog that gdal v. 1.8 was not find and application closed.
I checked with dependency walker what were was no gdal 1.8 dependency in
application and all