[gdal-dev] The proj.dll mistery

[Martin Chapman]

Joaquim,

I apologize that VantagePoint caused a problem for you.  We will make the
fix to the install and get the proj.dll out of the system32 directory.  Our
problem was that after upgrading to gdal 1.5x we could not get the proj dll
to load if it wasn't in the path and the only path it would work with was
the system32.

Sorry again,
Martin

-----Original Message-----
From: gdal-dev-bounces at lists.osgeo.org
[mailto:gdal-dev-bounces at lists.osgeo.org] On Behalf Of Joaquim Luis
Sent: Monday, June 30, 2008 4:47 PM
To: gdal-dev at lists.osgeo.org
Subject: [gdal-dev] The proj.dll mistery

Hi,

OK, I recovered from a  mysterious sudden stop working of my gdalwarp 
and ogrproj MEX files. All I had were error messages like

"Failed to create coordinate transformation between the
following coordinate systems.  This may be because they
are not transformable, or because projection services
(PROJ.4 DLL/.so) could not be loaded."

But not long ago those worked ok. It turn out that probably the culprit 
was the "VantagePoint" here pointed out recently, that installed an 
older (incompatible??) version of proj.dll on "C:\WINDOWS\system32"  (I 
hate softs that do it).

When I have dll conflicts, I always use the Dependency Walker to help me 
out, but in this case (an others??) the gdal.dll (trunk version) didn't 
show up any dependency on proj.dll. So it was a matter of "and what if 
it is in system32?" lucky guess that allowed me to solve the problem.
There are plenty of dll dependencies on gdal.dll. Why not on proj.dll?

Thanks

Joaquim Luis

_______________________________________________
gdal-dev mailing list
gdal-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev