[Gdal-dev] Visual Studio 2005, GDAL and Manifests

[Frank Warmerdam]

Simon Perkins wrote:
> (b) Compile everything with /MD, but disable optimization in those
> sections of code I want to debug. Also ensure that the _DEBUG flag is
> undefined everywhere to avoid _CrtDbgReportW() link errors.
> 
> I've been using (b) and so far it seems to be working fine. I can step
> through code, set breakpoints etc.

Simon,

This is what I do.  I use /MD and /Zi for debuggin and /MD and /Ox for
optimized releases.

> Out of curiosity, does using the debug CRT provide any benefit that
> anyone knows of? I guess it allows you to step into some of the standard
> C/C++ library routines, but that seems like a relatively small win for
> the extra pain...

My understanding is tha the /MDd CRT does extra runtime checking, watching
for heap corruption, and possible some stuff like illegal arguments to system
functions.  Perhaps better debugging into system functions?  However, whatever
it does has never seemed very important to me.

PS. with all due respect to Ben, I think that one can be quite functional,
including gui debugging, with GDAL built using makefile.vc.  I'm sure there
are advantages to using a fully project file based approach, but they are not
so enormous as to leave those using the makefiles crippled in comparison.  And
there are costs in complexity and maintainability for the project files.

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    | President OSGeo, http://osgeo.org