cURL / Mailing Lists / curl-library / Single Mail

curl-library

Re: Curl, Openssl and Makefile.m32

From: Niall Twomey <twomers_at_gmail.com>
Date: Sun, 16 Sep 2007 17:50:23 +0100

Good news! I downloaded zlib and copied the zdll.lib file and it all
compiles fine now!

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 ...
I'm making this:

int main(void) {
  CURL *curl;
  CURLcode res;

  curl = curl_easy_init();
  if(curl) {
    curl_easy_setopt(curl, CURLOPT_URL, "curl.haxx.se");
    res = curl_easy_perform(curl);
    curl_easy_cleanup(curl);
  }
  return 0;
}

I used that batch file I mentioned earlier so I have 11 different builds.
I'm pointing msvc to the "release" for the libs, and to "release-dll" for
the dlls ... that's what it means by "Executable Files", right? In MSVC++?

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?
Received on 2007-09-16