Initializes the GLib thread system. Before you use a thread related function in glibmm, you should initialize the thread system. This is done by calling Glib::thread_init().
- You should only call thread_init() with a non-
0 parameter if you really know what you are doing.
thread_init() must not be called directly or indirectly as a callback from glibmm. Also no mutexes may be currently locked while calling thread_init().
might only be called once. On the second call it will abort with an error. If you want to make sure that the thread system is initialized, you can do that too:
After that line either the thread system is initialized, or the program will abort if no thread system is available in GLib, i.e. either
is not defined or
If no thread system is available and vtable is
0 or if not all elements of vtable are non-
0, then thread_init() will abort.
- To use thread_init() in your program, you have to link with the libraries that the command
pkg-config --libs gthread-2.0 outputs. This is not the case for all the other thread related functions of glibmm. Those can be used without having to link with the thread libraries. (You have to link with
gthread-2.0 if you actually want to use threads in your application, though.)
|vtable ||A function table of type |
GThreadFunctions, that provides the entry points to the thread system to be used.
Definition at line 773 of file thread.h.