Re: CURLE_COULDNT_RESOLVE_HOST from CURLU API on https://www.google.com

2021-08-19 Thread Daniel Stenberg via curl-library
On Fri, 20 Aug 2021, Samuel Marks via curl-library wrote: curl_easy_setopt(curl, CURLOPT_URL, urlp); From the CURLOPT_URL man page: Pass in a pointer to the URL to work with. The parameter should be a char * to a null-terminated string which must be URL-encoded You seem to have intended

CURLE_COULDNT_RESOLVE_HOST from CURLU API on https://www.google.com

2021-08-19 Thread Samuel Marks via curl-library
I'm writing a tiny libcurl wrapper. I use curl_slist for headers, and your CURLU (URL API) for urls. https://github.com/SamuelMarks/curl-simple-https In https://github.com/SamuelMarks/curl-simple-https/blob/90e16a9/libcurl_simple_https/curl_simple_https.c the relevant lines that my `https_get`

Re: libcurl.a linker errors on XCode

2021-08-19 Thread Anmol Mishra via curl-library
So, here is an issue. Linking to this causes errors - /usr/local/Cellar/curl/7.78.0/lib/libcurl.a Using these flags allows for a build - -L/usr/local/Cellar/curl/7.78.0/lib -lcurl The problem is that -lcurl is probably bringing in the default system lib. And that is not something I want.

Re: libcurl.a linker errors on XCode

2021-08-19 Thread Daniel Stenberg via curl-library
On Thu, 19 Aug 2021, Anmol Mishra wrote: Using these flags allows for a build - -L/usr/local/Cellar/curl/7.78.0/lib -lcurl The problem is that -lcurl is probably bringing in the default system lib. And that is not something I want. When you build your application you use a linker. If that

Re: libcurl.a linker errors on XCode

2021-08-19 Thread Daniel Stenberg via curl-library
On Thu, 19 Aug 2021, Anmol Mishra wrote: Intuitively, these extra dependencies seems wrong. If I build a static version of a lib, it should not depend on a shared lib. You build a static version of libcurl. That's static. You then need to make sure to use whatever you want from the

Re: libcurl.a linker errors on XCode

2021-08-19 Thread Anmol Mishra via curl-library
-L/usr/local/Cellar/curl/7.78.0/lib -lcurl I have done this. In fact I specifically used the full path to libcurl.a to avoid picking up the macOS version. Intuitively, these extra dependencies seems wrong. If I build a static version of a lib, it should not depend on a shared lib.

Re: libcurl.a linker errors on XCode

2021-08-19 Thread Daniel Stenberg via curl-library
On Thu, 19 Aug 2021, Anmol Mishra via curl-library wrote: That makes sense. Is there a list of dependencies somewhere ? It depends entirely on your specific build. "sh curl-config --libs" should list them after a build. -- / daniel.haxx.se | Commercial curl support up to 24x7 is

Re: libcurl.a linker errors on XCode

2021-08-19 Thread Anmol Mishra via curl-library
That makes sense. Is there a list of dependencies somewhere ? From: Daniel Stenberg Sent: Thursday, 19 August 2021 9:10 AM To: Anmol Mishra via curl-library Cc: Anmol Mishra Subject: Re: libcurl.a linker errors on XCode On Thu, 19 Aug 2021, Anmol Mishra via

Re: libcurl.a linker errors on XCode

2021-08-19 Thread Daniel Stenberg via curl-library
On Thu, 19 Aug 2021, Anmol Mishra via curl-library wrote: I built a homebrew libcurl in a custom dir. The project is linking against this custom lib. I am getting 200+ linker errors. As far as I know, I followed the FAQ. I'm missing something very basic. It looks like you're building and

libcurl.a linker errors on XCode

2021-08-19 Thread Anmol Mishra via curl-library
I built a homebrew libcurl in a custom dir. The project is linking against this custom lib. I am getting 200+ linker errors. As far as I know, I followed the FAQ. I'm missing something very basic. My CFlags - -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT