I am using curl 7.13.2.

I am just trying to build. :) Doesn't matter command line or GUI.

I had successfully built openssl-0.9.7d. and then I followed the
instructions and did both nmake vc-ssl and nmake vc-ssl-release.

But when I tried to link my program that needs to link against
libcurl.lib, it reports quite a few unresolved symbol errors.

Like the following:

libcurl.lib(easy.obj) : error LNK2001: unresolved external symbol
__imp__WSACleanup_at_0
libcurl.lib(telnet.obj) : error LNK2001: unresolved external symbol
__imp__WSACleanup_at_0
libcurl.lib(easy.obj) : error LNK2001: unresolved external symbol
__imp__WSAStartup_at_8
libcurl.lib(telnet.obj) : error LNK2001: unresolved external symbol
__imp__WSAStartup_at_8
libcurl.lib(sendf.obj) : error LNK2001: unresolved external symbol
__imp__send_at_16
libcurl.lib(telnet.obj) : error LNK2001: unresolved external symbol
__imp__send_at_16
libcurl.lib(sendf.obj) : error LNK2001: unresolved external symbol
__imp__recv_at_16

My program linked just fine against libcurl.lib without SSL support, so
I don't think there is any wrong in the project settings.

Thanks.

Wei

Bradford Bruce wrote:

>Are you trying to build from the command line or the GUI?
>
>I've found the command line to be easier.
>
>Below is a section of makefile.vc6 included in the distribution.
>
>!MESSAGE Usage: nmake /f makefile.vc6 CFG=<config> <target>
>!MESSAGE where <config> is one of:
>!MESSAGE release - release static library
>!MESSAGE release-ssl - release static library with
>ssl
>!MESSAGE release-zlib - release static library with
>zlib
>!MESSAGE release-ssl-zlib - release static library with
>ssl and zlib
>!MESSAGE release-ssl-dll - release static library with
>dynamic ssl
>!MESSAGE release-zlib-dll - release static library with
>dynamic zlib
>!MESSAGE release-ssl-dll-zlib-dll - release static library with
>dynamic ssl and dynamic zlib
>!MESSAGE release-dll - release dynamic library
>!MESSAGE release-dll-ssl-dll - release dynamic library with
>dynamic ssl
>!MESSAGE release-dll-zlib-dll - release dynamic library with
>dynamic zlib
>!MESSAGE release-dll-ssl-dll-zlib-dll - release dynamic library with
>dynamic ssl and dynamic zlib
>!MESSAGE debug - debug static library
>!MESSAGE debug-ssl - debug static library with ssl
>!MESSAGE debug-zlib - debug static library with zlib
>!MESSAGE debug-ssl-zlib - debug static library with ssl
>and zlib
>!MESSAGE debug-ssl-dll - debug static library with
>dynamic ssl
>!MESSAGE debug-zlib-dll - debug static library with
>dynamic zlib
>!MESSAGE debug-ssl-dll-zlib-dll - debug static library with
>dynamic ssl and dynamic zlib
>!MESSAGE debug-dll - debug dynamic library
>!MESSAGE debug-dll-ssl-dll - debug dynamic library with
>dynamic ssl
>!MESSAGE debug-dll-zlib-dll - debug dynamic library with
>dynamic zlib1
>!MESSAGE debug-dll-ssl-dll-zlib-dll - debug dynamic library with
>dynamic ssl and dynamic zlib
>!MESSAGE <target> can be left blank in which case all is assumed
>
>Brad Bruce
>
>-----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 26, 2005 2:15 PM
>To: libcurl development
>Subject: Re: How to compile libcurl with SSL support on Windows?
>
>On Wed, 26 Oct 2005, Wei Weng wrote:
>
>
>
>>With visual studio.
>>
>>Any HOWTOs I can read?
>>
>>
>
>You read docs/INSTALL already and it didn't help? There's even a visual
>studio project file in the lib/ dir in the release archive, that not
>good
>enough either?
>
>Can you tell us a little bit about what your problems are?
>
>
>
Received on 2005-10-27