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 Colo
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 pro
Hi, I'm working with HDF4 and HDF5 using gdal in VS2008, and I get lots of
troubles which make me confused.
As all the guides said, I modified the nmake.opt like this;
MSVC_VER=1500
GDAL_HOME = "C:\GDAL\gdal-1.6.2\bld-162"
# Uncomment the following and update to enable NCSA HDF Release 4 support.
