[gnutls-devel] Automatic library initialization

Nikos Mavrogiannopoulos nmav at gnutls.org
Mon Nov 16 18:57:49 CET 2015

On Mon, Nov 16, 2015 at 6:10 PM, Andrew W. Nosenko
<andrew.w.nosenko at gmail.com> wrote:
>> >> Something like the following. Have each program not wishing to use
>> >> global initialization to define a symbol which overrides a weak one
>> >> from gnutls. In practice that would mean setting:
>> >> in some global section in your program. That can also be easily
>> >> backported in 3.3.x and you can check for that feature with an ifdef.
>> >> Would that be acceptable?
>> > Brilliant idea. I'll use it for my projects... but other projects won't
>> > benefit immediately (they first have to know).
>> I'll then include it in 3.4.x and 3.3.x releases.
> First at all, IMHO, _current_ API, which eliminates requirement to call
> explicitly some init function is a good.  And the "old-style API" with
> requirement to call some init function before any thread and/or child
> processes will be forked, which you want to resurrect, is a bad.

I believe you misunderstood the intention. There will be a way for
certain applications to disable the "automatic" initialization.
Otherwise, all other applications and libraries will take advantage of
that, and need not to call gnutls_global_init().


More information about the Gnutls-devel mailing list