[Gdal-dev] MSVCRT80.dll

Matt Hanson mhanson at photon.com
Mon Sep 11 22:50:38 EDT 2006


I have Visual Studio 2005 Prof, so I'm not sure what this redistributable package would add.
 
I've been using GDAL fine in my app, but then I tried to upgrade to the latest version and this problem cropped up again, trying to go back to the stable version results in the same problem.   ack

________________________________

From: Ned Harding [mailto:nharding at extendthereach.com]
Sent: Mon 9/11/2006 10:48 PM
To: Matt Hanson; Gdal-dev at lists.maptools.org
Subject: RE: [Gdal-dev] MSVCRT80.dll



MS changed the way the dlls install for VS2005.  The easiest way to deal
with it is to just use their install to make sure they are all in the
right places.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=
32BC1BEE-A3F9-4C13-9C99-220B62A191EE

Ned.

-----Original Message-----
From: gdal-dev-bounces at lists.maptools.org
[mailto:gdal-dev-bounces at lists.maptools.org] On Behalf Of Matt Hanson
Sent: Monday, September 11, 2006 8:33 PM
To: Gdal-dev at lists.maptools.org
Subject: [Gdal-dev] MSVCRT80.dll

I'm not sure how exactly I did things differently, but I got the latest
snapshot for the SetMetadataItem fix and compiled using nmake as per the
Windows install directions.   I overwrote my gdal13.dll and
gdal13.dll.manifest files and I'm getting a error:

"This application has failed to start because MSVCR80.dll was not found.
Re-installing the application may fix the problem"

I'm using nmake.opt as is except for changing the directory.   I also
edited cpl_config.h.vc to set the vnsprintf and related functions to 0.

Now it's important to note that I did get this error when I first tried
to install GDAL but ended up solving it by copying the dll and manifest
files to the directory where my exe is located.   But this time it
doesn't work.  I even went back to the 1.3.2 release version and am
getting the same error.   Also note I have followed all old suggestions
on the forums concerning this and they don't work.  This is somehow
related to debug information.

Has anyone else encountered this?   This problem drove me nuts for hours
the first time and I'd rather not repeat it.

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






More information about the Gdal-dev mailing list