Hi,
> Good news! I downloaded zlib and copied the zdll.lib file and it all
> compiles fine now!
I though strongly recommend that you build zlib self (to avoid whoes because of different compiler and / or switches); its very easy, and works similar as libcurl from commandline; just read the comment in ./win32/Makefile.msc

> I'm getting linking errors when I use msvc with it though. I've pointed
> msvc
> to the right places (for zlib, openssl, and curl), but I get this:

>>> CURL.obj : error LNK2001: unresolved external symbol "enum CURLcode
> __cdecl curl_easy_setopt(void *,enum CURLoption,...)"
> (?curl_easy_setopt@@$$J0YA?AW4CURLcode@@PAXW4CURLoption@@ZZ)
>>> CURL.obj : error LNK2001: unresolved external symbol "void __cdecl
> curl_easy_cleanup(void *)" (?curl_easy_cleanup@@$$J0YAXPAX_at_Z)
>>> CURL.obj : error LNK2001: unresolved external symbol "enum CURLcode
> __cdecl curl_easy_perform(void *)"
> (?curl_easy_perform@@$$J0YA?AW4CURLcode@@
> PAX_at_Z)
>>> CURL.obj : error LNK2001: unresolved external symbol "void * __cdecl
> curl_easy_init(void)" (?curl_easy_init@@$$J0YAPAXXZ)

> I'm confident that I'm pointing to the right places too ...
read here:
http://curl.haxx.se/docs/faq.html#Link_errors_when_building_libcur

> Never mind ... it's working now ... apparently :) I just but all the
> necessary dlls, libs, res and exp in the same place.

> I get this output for the simple https.c:

> * About to connect() to sourceforge.net port 443 (#0)
> * Trying 66.35.250.203... * connected
> * Connected to sourceforge.net (66.35.250.203) port 443 (#0)
> * SSL certificate problem, verify that the CA cert is OK. Details:
> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify
> failed
> * Closing connection #0
> * Peer certificate cannot be authenticated with known CA certificates

> Which I got rid of my removing the ifdef for peer verification ... seems
> like a bit of a hack though. Should I worry about it?
that's just the way how SSL works; normally you need to specify the ca-bundle.crt, and probably also need to append your remote host CA to that file; however if you dont care for CA verifcation then just use the 'hack'; but realize that its less secure.

Guenter.
Received on 2007-09-16