I've fixed it rather dirty, but it has to be something alongside this:

release: $(RELEASE_OBJS)
        $(LINKR) $(LFLAGS) $(LINKLIBS) $(RELEASE_OBJS)
        mt -manifest curl.exe.manifest -outputresource:curl.exe;1

debug: $(DEBUG_OBJS)
        $(LINKD) $(LFLAGS) $(LINKLIBS_DEBUG) $(DEBUG_OBJS)
        mt -manifest curl.exe.manifest -outputresource:curl.exe;1
 
;1 in this case means we're embedding manifest into an executable. In
case of embedding manifest into a shared library it has to be ;2

For more information, please refer to
http://msdn2.microsoft.com/en-us/library/ms235591(VS.80).aspx

Regards,
Vladimir

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Daniel Stenberg
Sent: Wednesday, October 24, 2007 10:21
To: libcurl development
Subject: RE: curl & MSVC 8

On Wed, 24 Oct 2007, Vladimir Lazarenko wrote:

> Umm, nevermind, fixed by adding the missing lib to the Makefile.

I believe this is fixed in the recent snapshots. Can you please verify?

> VC8 by default generates manifest files for the executables. Default
> behavior in MSVC is to embed the manifest into the resulting
executable.
> This is not done in curl Makefiles for VC8, resulting in a useless
> .exe in case you don't distribute the manifest alongside.
>
> Could that be fixed? (I fixed that internally, but still)

Uhm, how? Can you post a patch or an explanation on what needs to be
done?

--
  Commercial curl and libcurl Technical Support:
http://haxx.se/curl.html