[gdal-dev] Missing msvcr80.dll ?
Martin Chapman
chapmanm at pixia.com
Sat Sep 5 17:22:34 EDT 2009
Mateusz,
I agree. MD is what I always use. Once you figure out the manifest stuff
things become easier. On another note, I was checking out the GD lib
homepage a few weeks ago and ended up looking at your home page. Those
cliffs near the water where you rock climb look awesome! I live in Colorado
and use to climb a lot when I was younger. Really cool pics!
Martin
-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net]
Sent: Saturday, September 05, 2009 3:17 PM
To: Stefan Moebius
Cc: Martin Chapman; gdal-dev at lists.osgeo.org; 'Martin Hvidberg'
Subject: Re: [gdal-dev] Missing msvcr80.dll ?
Stefan Moebius wrote:
> Another solution for avoiding pain for users is to link msvcrt
> statically. For this you need to change the compiler switch /MD into /MT
> (/MDd to /MTd for debug).
In the world of Windows OS, DLL is the preferred option.
Static linking to C/C++ run-time can cause more problems than it helps.
Check the Caution paragraph:
http://msdn.microsoft.com/en-us/library/2kzt1wy3(VS.71).aspx
> Note that if you link against external
> libraries (like geos, proj4, etc.), you need to recompile those too with
> the same change.
That's exactly the evil of static linking. Users would need to recompile
all components of their software.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
More information about the gdal-dev
mailing list