[gdal-dev] ImportError when importing gdal module with python 2.7 on Windows 7 64-bit

[Rutger]

Hi George,

You can also open the _gdal.pyd with Dependency Walker, i think thats the
file which is actually being opened when the traceback is returned. In
addition to gdal.dll it also check for python27.dll and kernel32.dll. 
The ISHIMS.DLL is not a problem for as far as i know.

Normally you should be able to resolve MSVCR80.DLL issues by installing the
appropriate MS Visual C++ Redistributable (if you havent done so already),
the version *80.dll would mean that you need the 2005 version.

Microsoft Visual C++ 2005 Redistributable Package (x86)
http://www.microsoft.com/en-us/download/details.aspx?id=3387

or 

Microsoft Visual C++ 2005 Redistributable Package (x64)
http://www.microsoft.com/en-us/download/details.aspx?id=21254

If im correct:
msvcr80.dll = Microsoft Visual C++ 2005
msvcr90.dll = Microsoft Visual C++ 2008
msvcr100.dll = Microsoft Visual C++ 2010

But installing it didnt resolve the issue for me. If Joaquim is correct,
only compiling Python and GDAL with the same version of the compiler would
help. Can you see which compiler was used, and which one you need? Both my
Python and GDAL dlls seem to point to the same msvc90.dll file. 

If i open my _gdal.pyd in Dependency Walker i see gdal.dll links twice to
exactly the same dll, and Dependency Walker complains in only one occasion.
Its a complete mystery to me....

<http://osgeo-org.1560.n6.nabble.com/file/n5016933/Depency_walker_gdal.png> 


Regards,
Rutger






--
View this message in context: http://osgeo-org.1560.n6.nabble.com/gdal-dev-ImportError-when-importing-gdal-module-with-python-2-7-on-Windows-7-64-bit-tp5006198p5016933.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.