<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
OK, got it all to work...<br>
<br>
The issue is explained here:<br>
<br>
<a class="moz-txt-link-freetext" href="http://forums.microsoft.com/msdn/showpost.aspx?postid=15218&siteid=1">http://forums.microsoft.com/msdn/showpost.aspx?postid=15218&siteid=1</a><br>
<br>
Basically, VS 2005 applications now require a manifest which basically
specifies which version of the runtime library an executable should
link against. This makes executables much more tightly bound to the DLL
versions that they load. When you build the application with the visual
C++ IDE, the manifest gets embedded inside the executable and you don't
have to worry about it. However, for some reason, when you build using
nmake, the manifest is produced as an additional file, with the
extension .manifest. In order to run the executable, you have to have
that manifest in the same directory as the executable. The problem I
was seeing is that the GDAL makefile.vc install target doesn't copy
these manifest files. I updated apps/makefile.vc to install the
.exe.manifest files alongside the .exe files, and now everything works
great! Ditto for the gdal13.dll.manifest file. I'll commit a fix to CVS
shortly.<br>
<br>
Apparently, it is possible to embed the manifest into the executable
with a certain amount of jiggery pokery, as described here:<br>
<br>
<a class="moz-txt-link-freetext" href="http://msdn2.microsoft.com/en-us/library/ms235591.aspx">http://msdn2.microsoft.com/en-us/library/ms235591.aspx</a><br>
<br>
Seems like a lot of work to me, so I haven't bothered implementing
that. If anyone else feels up to it, please go ahead!<br>
<br>
Cheers,<br>
<br>
Sy<br>
<br>
P.S. As I finish this, I see that Mateusz has posted something
suggesting basically the same solution, but I'll send this anyway...<br>
<br>
Simon Perkins wrote:
<blockquote cite="mid43B5BD19.50809@perkins.net" type="cite">
<meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type">
Hi Mateusz,<br>
<br>
Thanks for the suggestions. I've followed the instructions on that page
and made the required changes to atlbase.h and atlwin.h, and installed
WTL. I then did a complete clean and rebuild of GDAL. However, I get
the same result as with the simple fix I reported earlier: the build no
longer complains about not finding atlthunk.lib, but I get a strange
failure to find MSVCR80.dll when trying to run any of the GDAL
utilities from the command line. Anybody else seen this? I wonder if it
is a "feature" of building win32 applications with visual studio 2005
express?<br>
<br>
Cheers,<br>
<br>
Sy<br>
<br>
<br>
Mateusz Łoskot wrote:
<blockquote cite="mid54627.127.0.0.1.1135980967.squirrel@loskot.net"
type="cite">
<pre wrap="">On Fri, Dec 30, 2005 11:02 pm, Simon Perkins wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Some updates. I found a suggestion on the web to simply comment out the
line #pragma comment(lib, "atlthunk.lib") from the atlbase.h file (found
in C:\Program Files\Microsoft Platform SDK\include\atl after you install
the platform SDK).
[...]>
Has anyone managed to build GDAL using the express edition of Visual C++
2005?
</pre>
</blockquote>
<pre wrap=""><!---->
Have you read my last response?
Have you tried solution from WTL group I included in my post?
Cheers
</pre>
</blockquote>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Gdal-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gdal-dev@lists.maptools.org">Gdal-dev@lists.maptools.org</a>
<a class="moz-txt-link-freetext" href="http://lists.maptools.org/mailman/listinfo/gdal-dev">http://lists.maptools.org/mailman/listinfo/gdal-dev</a></pre>
</blockquote>
</body>
</html>