On Mon, 27 Jan 2020, Srikar via curl-library wrote:
Hi, Am Porting libcurl to Embedded Platform without OS/Socket Libraries I
have configured curl_config.h based on Embedded Platform which do not have
Socket libraries ,but still needs curl_struct_sockaddr support from Platform
to compile My Questions.
I would imagine that the easier way to do this is to provide those functions
yourself in your glue layer
1.Can we configure Libcurl to use http/ssl always (restrict usage of TCP
protocol only for SSL Layer and Libcurl always access SSL Layer for
communication) ?
Nope. There's no existing build-time option for curl to build it without
support for clear text protocols. But bou can limit the build to HTTP(S) only,
and then you can limit it HTTPS only at run-time using the API.
2. Is curl_struct_sockaddr mandatory if we like to skip libcurl
interaction with TCP layer ?
That's not for "TCP layer", that's for name resolving and yes libcurl will
presume that you can resolve host names to addresses.
(And I'll just note that curl_struct_sockaddr doesn't exist in curl, but it is
part of the tiny-curl patch.)
3. If curl_struct_sockaddr is mandatory?
Well, that's how I solved the problem in tiny-curl. If the platform has its
own addrinfo struct I found that a convenient way to do it. If you have a
better way then go ahead.
What functions need to be provided for libcurl ?
I don't have a list. If you link with libcurl I'm sure the linker will tell
you which functions it misses! =)
--
/ daniel.haxx.se | Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
