[Gdal-dev] Tracing into GDAL
ben at vterrain.org
Thu Aug 14 11:51:54 EDT 2003
gdal_i.lib definitely! The static gdal library is huge, especially the
debug version. gdal_i.lib/gdal11.dll, and the debug versions
gdal_id.lib/gdal11d.dll are quite compact, relatively speaking. On my
machine, it's 20MB vs. 2MB/3MB.
> -----Original Message-----
> From: gdal-dev-admin at remotesensing.org
> [mailto:gdal-dev-admin at remotesensing.org] On Behalf Of mathieu_gdal
> Sent: Thursday, August 14, 2003 10:13 AM
> To: gdal-dev at remotesensing.org
> Subject: RE : [Gdal-dev] Tracing into GDAL
> Thank you for the answer, but...
> it does not work on my computer!
> Do you use gdal_i.lib or gdal.lib?
> -----Message d'origine-----
> De : gdal-dev-admin at remotesensing.org
> [mailto:gdal-dev-admin at remotesensing.org] De la part de Ben Discoe
> Envoyé : mercredi 13 août 2003 16:46
> À : gdal-dev at remotesensing.org
> Objet : RE: [Gdal-dev] Tracing into GDAL
> You don't need to "put gdal11.pdb in my app's application". Leave all
> files such as .pdb in their original locations (generally
> with the .lib)
> so that they will be found. You should be able to trace into GDAL
> functions with MSVC; i do it all the time.
More information about the Gdal-dev