Hi folks,
For what it's worth, what enabled me to find the conflict with
libeay32.dll on my machine, was the method outlined earlier:
* opening a fresh command shell,
* completely stripping all PATH and PYTHON* environment variables,
* slowly adding the paths back in one at a time until the problem
resurfaced,
* examining the contents of latest folder added,
* remove .dll's from that folder until it works again
I'm not that familiar with Dependency Walker but when looking at
"Options > Module Search Order" I see it does make use of the PATH of
whichever shell started it -- meaning you need to start depends.exe from
within the Osgeo4w shell or it will use the default Windows user profile
environment instead.
cheers,
matt wilkie
--------------------------------------------
Geomatics Analyst
Information Management and Technology
Yukon Department of Environment
10 Burns Road * Whitehorse, Yukon * Y1A 4Y9
867-667-8133 Tel * 867-393-7003 Fax
http://environmentyukon.gov.yk.ca/geomatics/
--------------------------------------------
On 13-Jun-2012 12:53 AM, Casper Børgesen (CABO) wrote:
I'm aware of the difference in Python versions with OSGEO and my setup, but so
far I have assumed that the solution to the problems related to the DLLs
probably is the same regardless of the python/gdal version.
With regards to the VM, linux is not a solution a the moment - IT policies and
so on :)
A follow up on topic:
I found that the two MSVCP100.dll and MSVCR100.dll is part of the Microsoft
Visual C++ redistribution package and by installing that I actually got GDAL
1.9 and Python 3.2 to work with an empty PATH (except for my references to the
network drive of course). Error references to IESHIMS.DLL in the Dependency
Walker thus seems like being a wild chase.
My PATH contain references to:
\\drive\Python32
\\drive\GDAL19
I don't remember where I found the compilations of the two, but I haven't
compiled them myself.
Now I need to find somewhere to create an installation of OSGEO to see if I can
track down the problem there. Maybe it has something to do with the
libeay32.dll (which in my case is related to GNU...something on the path) like
Matt found out.
Thanks for your comments!
Regards Casper
_______________________________________________
osgeo4w-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
