sergiotarxz
/
libvips
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

more VIPS_INIT() docs 

see https://github.com/jcupitt/libvips/issues/588
This commit is contained in:
John Cupitt 2017-01-26 08:46:27 +00:00
parent 7136053451
commit 276fc83fa1
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
libvips/iofuncs/init.c
View File

@ -135,8 +135,13 @@ vips_get_argv0( void )
* therefore be unable to find its data files. It is much better to call * therefore be unable to find its data files. It is much better to call
* this macro yourself. * this macro yourself.
* *
* VIPS_INIT() is a macro, since it tries to check binary compatibility * Additionally, VIPS_INIT() can be run from any thread, but it must not be
* between the caller and the library. * called from more than one thread at the same time. This is much easier to
* guarantee if you call it yourself.
*
* VIPS_INIT() is a macro, since it tries to check ABI compatibility
* between the caller and the library. You can also call vips_init(), the
* non-macro version, if macros are not available to you.
* *
* You may call VIPS_INIT() many times and vips_shutdown() many times, but you * You may call VIPS_INIT() many times and vips_shutdown() many times, but you
* must not call VIPS_INIT() after vips_shutdown(). In other words, you cannot * must not call VIPS_INIT() after vips_shutdown(). In other words, you cannot
@ -249,7 +254,6 @@ vips_load_plugins( const char *fmt, ... )
* *
* Returns: 0 on success, -1 otherwise * Returns: 0 on success, -1 otherwise
*/ */
int int
vips_init( const char *argv0 ) vips_init( const char *argv0 )
{ {