[gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?

Clay, Bruce bclay at ball.com
Tue Dec 16 15:36:11 EST 2008

  I am trying to run ogrinfo from the GDAL build app directory.  I did
not have a problem with this until my computer died and I had to get a
new one with you guessed it Vista.  It is a 64 bit system running 64 bit
Vista so that may be part of the problem.  

Did you build with the manifest as part of the build process or just add
it to the runtime directory?

Did you build the whole package with VS 2008 nor just the GEOS portion?

I have run into other problems on this computer mainly with drivers.  My
Microsoft finger print reader is not supported on 64 bit.  It makes me
wonder just what MS is thing some times, actually most of the time.
They keep changing things that don't help at all.

-----Original Message-----
From: Frank Warmerdam [mailto:warmerdam at pobox.com] 
Sent: Tuesday, December 16, 2008 3:13 PM
To: Clay, Bruce
Cc: gdal-dev at lists.osgeo.org
Subject: Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?

Clay, Bruce wrote:
> Frank:
>   What is the secret to getting GDAL to build this way?  I have Visual
> Studio 2005 and have not been able to get it to run.  The zip file you
> posted works fine on my system (Vista 64 Bit) but it does not include
> the csharp files so I have to build.
> I have tried building with the makefile.vc file and with the solution
> file.
> In both cases it compiles fine but won't run.  I get an error popup
> I try to run ogrinfo that says
>  "An application has made an attempt to load the C runtime library
> without using a manifest.  This is an unsupported way to load Visual
> Studio C++ libraries" etc.


I'm not sure what issue(s) you are running into exactly.  Is this just
running something like gdalinfo that you build against the GDAL16.DLL
that you built?

The only "special" thing I do for the GEOS part of the build which I
build with visual studio 9 (aka 2008 express I think) was to ensure
I distributed the msvcp90.dll and msvcr90.dll along with the

I think that Visual Studio 2005 is VC8, so there should be a
msvc{r,p}80.dll you would need with it, and perhaps a corresponding
manifest.  I haven't been using VS2005 much though so I'm not so sure.

These issues (needing a manifest) don't exist with older visual studio

Best regards,
I set the clouds in motion - turn up   | Frank Warmerdam,
warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

More information about the gdal-dev mailing list