[Gdal-dev] GDAL Manifest Changes
mateusz at loskot.net
Fri Nov 3 03:40:59 EST 2006
Simon Perkins wrote:
> Visual Studio / makefile.vc people:
> I've just checked some small changes into makefile.vc, apps/makefile.vc
> and ogr/Makefile to automatically embed manifests into DLLs and EXEs, if
> they are generated. Shouldn't have any effect unless you're using VS
> 2005. I also removed the lines I added a few months ago to install
> manifest files into the install directories for the install target,
> since this is no longer necessary. Manifest files are also cleaned up by
> the clean target.
> This should eliminate some mysterious "MSVCR80.DLL not found" problems
> you may encounter when linking against GDAL built using VS 2005.
> Basically, every DLL and EXE target now has an additional line that
> looks something like:
> if exist $(SOME_DLL).manifest mt -manifest $(SOME_DLL).manifest
> if exist $(SOME_EXE).manifest mt -manifest $(SOME_EXE).manifest
Today, I was asked for Windows XP version of some Shapelib utils,
so I decided to do small test of your idea.
I did build DLL and .exe utils from PROJ.4 4.5.0 and Shapelib 1.2.10,
according to this guidelines, using Visual C++ 2005.
I applied appropriate changes to makefile.vc files in PROJ.4 and
Shapelib sources and made .exe utils linking dynamically with DLLs.
Shortly, it works for me well.
Here are sources with my changes:
Note, all makefile.vc files I changed got appropriate comment
at the beginning.
Here are binaries compiled and ready to test:
Note, all .exe files load dynamically shapelib.dll and/or proj.dll,
so check if there are no old versions of these libraries in your
I think this short test is good to touch & feel Simon's concept.
More information about the Gdal-dev