mirror of
https://github.com/curl/curl.git
synced 2026-07-24 20:37:17 +03:00
global_init() takes a flag option now, to tell libcurl what _not_ to init.
it will make it better when the application uses several libs that use openssl and it also enables us to do the win32 winsock initing in the future if we want to
This commit is contained in:
parent
ce0e2cc017
commit
f44f512f24
2 changed files with 15 additions and 2 deletions
|
|
@ -8,7 +8,7 @@ curl_global_init - Global libcurl initialisation
|
|||
.SH SYNOPSIS
|
||||
.B #include <curl/curl.h>
|
||||
.sp
|
||||
.BI "CURLcode curl_global_init(void);"
|
||||
.BI "CURLcode curl_global_init( " long flags " );"
|
||||
.ad
|
||||
.SH DESCRIPTION
|
||||
This function should be called once (no matter how many threads or libcurl
|
||||
|
|
@ -17,6 +17,9 @@ sessions that'll be used) by every application that uses libcurl.
|
|||
If this function hasn't been invoked when \fIcurl_easy_init\fP is called, it
|
||||
will be done automatically by libcurl.
|
||||
|
||||
The flags option should be set to zero. It will be used to tell libcurl what
|
||||
specific features it should \fBnot\fP init.
|
||||
|
||||
You must however \fBalways\fP use the \fIcurl_global_cleanup\fP function, as
|
||||
that cannot be called automatically for you by libcurl.
|
||||
.SH RETURN VALUE
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue