[Gdal-dev] Visual Studio 2005, GDAL and Manifests
sy at perkins.net
Wed Oct 25 16:01:02 EDT 2006
Thanks to everyone for the discussion on this matter - it's cleared up
several issues for me as to how to make this Visual Studio thing work.
Guess I didn't look at Ben's project files quite as closely as I should
On Wed, 25 Oct 2006 09:12:47 -1000, "Ben Discoe" <ben at vterrain.org>
> > do you build GDAL and then manually copy the DLLs
> > from the release or debug directories (as appropriate) into
> > a common directory that is on your PATH? Or do you modify
> > the GDAL build configurations so that both debug and release
> > versions get built in the same directory
> Have you tried using the gdal sln/vcproj files, provided on our page,
> gdal.org links to in the GDAL build instruction?
> You'll find that there is no manual copy (certainly not :) but instead a
> 'post-build step' which puts the DLLs into gdal\distro\bin, and the LIBs
> into gdal\distro\lib.
> This way, you only have to build GDAL once, when there is a new release.
> You point your system PATH to distro\bin, your VC libpath tp distro\lib,
> you're set.
> Or (if you're not picky about GDAL's configuration) you can just download
> the GDAL 'distro', from that same page, and avoid the whole process of
> building it.
> Gdal-dev mailing list
> Gdal-dev at lists.maptools.org
More information about the Gdal-dev