Hello,
I have an app that links statically against libcurl, which itself (libcurl)
is built with openssl support. My app is cross-compiled on Linux with
mingw-64 and run on Win7-64. The problem I'm facing is the following:
Unless I use the CURLOPT_CAINFO option and hard-code a certificate path,
Mason wrote:
I'm trying to cross-compile libcurl for an embedded platform
where the typical BSD socket functions are stored in a
static library as lwip_gethostbyname, lwip_connect, etc
(provided by lwip).
I'm still trying to run the configure script successfully.
It seems I can prevent
Hello everyone,
I'm trying to cross-compile libcurl for an embedded platform
where the typical BSD socket functions are stored in a
static library as lwip_gethostbyname, lwip_connect, etc
(provided by lwip).
I'm still trying to run the configure script successfully.
It seems I can prevent the
On Behalf Of Mason
Sent: Tuesday, February 28, 2012 08:47
Hello everyone,
I'm trying to cross-compile libcurl for an embedded platform
where the typical BSD socket functions are stored in a
static library as lwip_gethostbyname, lwip_connect, etc
(provided by lwip).
I'm still trying
On Tue, Feb 28, 2012 at 09:41:11AM -0800, Gary Maxwell wrote:
It has been about five years since I built libcurl to link
against lwip. A lot has happened to both libraries since then,
but it still seems true that ./configure will not be able
to make sense of the lwip libraries and headers.
I got more details for the described problem.
Seems that pipelining is working, I configured Nginx to print the status of
pipelining by using directive $pipe in log format. And almost in 70% of
request has used pipeline.
I decided to check is there are real async or not, I sent bunches with
On Tue, Feb 28, 2012 at 06:10:08PM +0400, ru-17 wrote:
I got more details for the described problem.
Seems that pipelining is working, I configured Nginx to print the
status of pipelining by using directive $pipe in log format. And
almost in 70% of request has used pipeline.
I assume you're
Alex Loukissas a...@maginatics.com wrote:
I have an app that links statically against libcurl, which itself (libcurl)
is built with openssl support. My app is cross-compiled on Linux with
mingw-64 and run on Win7-64. The problem I'm facing is the following:
Unless I use the CURLOPT_CAINFO
Dan Fandrich d...@coneharvesters.com wrote:
curl very much expects a BSD-style socket library. The best bet is to
write a shim library that calls the LWIP socket functions using the
standard names so that configure can find them.
lwIP already has this shim built-in.
Ref.
On Tue, Feb 28, 2012 at 09:34:40PM +0100, Gisle Vanem wrote:
lwIP already has this shim built-in.
Ref. src/include/lwip/sockets.h:
#if LWIP_COMPAT_SOCKETS
#define accept(a,b,c) lwip_accept(a,b,c)
#define bind(a,b,c) lwip_bind(a,b,c)
#define shutdown(a,b)
Dan Fandrich d...@coneharvesters.com wrote:
Do the shim include files mirror the POSIX socket include files? If so,
then adding something like CPPFLAGS=-Isrc/include/lwip/ to the configure
like ought to make configure curl pick them up. If not, it's trickier.
I'm not sure about non-Windows;
11 matches
Mail list logo
