Top |
Functions
gboolean | (*VipsOperationBuildFn) () |
VipsOperationFlags | vips_operation_get_flags () |
void | vips_operation_class_print_usage () |
void | vips_operation_invalidate () |
int | vips_operation_call_valist () |
VipsOperation * | vips_operation_new () |
int | vips_call_required_optional () |
int | vips_call () |
int | vips_call_split () |
int | vips_call_split_option_string () |
void | vips_call_options () |
int | vips_call_argv () |
void | vips_cache_drop_all () |
VipsOperation * | vips_cache_operation_lookup () |
void | vips_cache_operation_add () |
int | vips_cache_operation_buildp () |
VipsOperation * | vips_cache_operation_build () |
void | vips_cache_print () |
void | vips_cache_set_max () |
void | vips_cache_set_max_mem () |
int | vips_cache_get_max () |
int | vips_cache_get_size () |
size_t | vips_cache_get_max_mem () |
int | vips_cache_get_max_files () |
void | vips_cache_set_max_files () |
void | vips_cache_set_dump () |
void | vips_cache_set_trace () |
void | vips_concurrency_set () |
int | vips_concurrency_get () |
Description
The VipsOperation class and associated types and macros.
VipsOperation is the base class for all operations in libvips. It builds on VipsObject to provide the introspection and command-line interface to libvips.
It also maintains a cache of recent operations. See below.
vips_call(), vips_call_split()
and vips_call_split_option_string()
are used
by vips to implement the C API. They can execute any VipsOperation,
passing in a set of required and optional arguments. Normally you would not
use these functions directly: every operation has a tiny wrapper function
which provides type-safety for the required arguments. For example,
vips_embed()
is defined as:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
int vips_embed( VipsImage *in, VipsImage **out, int x, int y, int width, int height, ... ) { va_list ap; int result; va_start( ap, height ); result = vips_call_split( "embed", ap, in, out, x, y, width, height ); va_end( ap ); return( result ); } |
Use vips_call_argv()
to run any vips operation from a command-line style
argc/argv array. This is the thing used by the vips main program to
implement the vips command-line interface.
VipsOperation and reference counting
After calling a VipsOperation you are responsible for unreffing any output objects. For example, consider:
1 2 3 4 5 |
VipsImage *im = ...; VipsImage *t1; if (vips_invert (im, &t1, NULL)) error .. |
This will invert im
and return a new VipsImage, t1
. As the caller
of vips_invert()
, you are responsible for t1
and must unref it when you no
longer need it. If vips_invert()
fails, no t1
is returned and you don't
need to do anything.
If you don't need to use im
for another operation,
you can unref im
immediately after the call. If im
is needed to calculate
t1
, vips_invert()
will add a ref to im
and automatically drop it when t1
is unreffed.
Consider running two operations, one after the other. You could write:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
VipsImage *im = ...; VipsImage *t1, *t2; if (vips_invert (im, &t1, NULL)) { g_object_unref (im); return -1; } g_object_unref (im); if (vips_flip (t1, &t2, VIPS_DIRECTION_HORIZONTAL, NULL)) { g_object_unref (t1); return -1; } g_object_unref (t1); |
This is correct, but rather long-winded. libvips provides a handy thing to make a vector of auto-freeing object references. You can write this as:
1 2 3 4 5 6 7 |
VipsObject *parent = ...; VipsImage *im = ...; VipsImage *t = (VipsImage **) vips_object_local_array (parent, 2); if (vips_invert (im, &t[0], NULL) || vips_flip (t[0], &t[1], VIPS_DIRECTION_HORIZONTAL, NULL)) return -1; |
where parent
is some enclosing object which will be unreffed when this
task is complete. vips_object_local_array()
makes an array of VipsObject
(or VipsImage, in this case) where when parent
is freed, all non-NULL
VipsObject in the array are also unreffed.
The VipsOperation cache
Because all VipsObject are immutable, they can be cached. The cache is
very simple to use: instead of calling vips_object_build()
, call
vips_cache_operation_build()
. This function calculates a hash from the
operations's input arguments and looks it up in table of all recent
operations. If there's a hit, the new operation is unreffed, the old
operation reffed, and the old operation returned in place of the new one.
The cache size is controlled with vips_cache_set_max()
and friends.
Functions
vips_operation_get_flags ()
VipsOperationFlags
vips_operation_get_flags (VipsOperation *operation
);
Returns the set of flags for this operation.
vips_operation_class_print_usage ()
void
vips_operation_class_print_usage (VipsOperationClass *operation_class
);
Print a usage message for the operation to stdout.
[skip]
vips_operation_call_valist ()
int vips_operation_call_valist (VipsOperation *operation
,va_list ap
);
vips_operation_new ()
VipsOperation *
vips_operation_new (const char *name
);
Return a new VipsOperation with the specified nickname. Useful for language bindings.
You'll need to set
any arguments and build the operation before you can use it. See
vips_call()
for a higher-level way to make new operations.
[constructor]
vips_call_required_optional ()
int vips_call_required_optional (VipsOperation **operation
,va_list required
,va_list optional
);
This is the main entry point for the C and C++ varargs APIs. operation
is executed, supplying required
and optional
arguments.
Beware, this can change operation
to point at an old, cached one.
vips_call ()
int vips_call (const char *operation_name
,...
);
vips_call() calls the named operation, passing in required arguments and then setting any optional ones from the remainder of the arguments as a set of name/value pairs.
For example, vips_embed()
takes six required arguments, in
, out
, x
, y
,
width
, height
, and has two optional arguments, extend
and background
.
You can run it with vips_call()
like this:
1 2 3 4 5 6 7 |
VipsImage *in = ... VipsImage *out; if( vips_call( "embed", in, &out, 10, 10, 100, 100, "extend", VIPS_EXTEND_COPY, NULL ) ) ... error |
Normally of course you'd just use the vips_embed()
wrapper function and get
type-safety for the required arguments.
See also: vips_call_split()
, vips_call_options()
.
Parameters
operation_name |
name of operation to call |
|
... |
required args, then a |
vips_call_split_option_string ()
int vips_call_split_option_string (const char *operation_name
,const char *option_string
,va_list optional
,...
);
vips_cache_drop_all ()
void
vips_cache_drop_all (void
);
Drop the whole operation cache, handy for leak tracking. Also called
automatically on vips_shutdown()
.
vips_cache_operation_lookup ()
VipsOperation *
vips_cache_operation_lookup (VipsOperation *operation
);
Look up an unbuilt operation
in the cache. If we get a hit, ref and
return the old operation. If there's no hit, return NULL.
vips_cache_operation_add ()
void
vips_cache_operation_add (VipsOperation *operation
);
Add a built operation to the cache. The cache will ref the operation.
vips_cache_operation_buildp ()
int
vips_cache_operation_buildp (VipsOperation **operation
);
Look up operation
in the cache. If we get a hit, unref operation
, ref the
old one and return that through the argument pointer.
If we miss, build and add operation
.
[skip]
vips_cache_operation_build ()
VipsOperation *
vips_cache_operation_build (VipsOperation *operation
);
A binding-friendly version of vips_cache_operation_buildp()
.
After calling this, operation
has the same ref count as when it went in,
and the result must be freed with vips_object_unref_outputs()
and
g_object_unref()
.
vips_cache_print ()
void
vips_cache_print (void
);
Print the whole operation cache to stdout. Handy for debugging.
vips_cache_set_max ()
void
vips_cache_set_max (int max
);
Set the maximum number of operations we keep in cache.
vips_cache_set_max_mem ()
void
vips_cache_set_max_mem (size_t max_mem
);
Set the maximum amount of tracked memory we allow before we start dropping
cached operations. See vips_tracked_get_mem()
.
libvips only tracks memory it allocates, it can't track memory allocated by
external libraries. If you use an operation like vips_magickload()
, most of
the memory it uses won't be included.
See also: vips_tracked_get_mem()
.
vips_cache_get_max ()
int
vips_cache_get_max (void
);
Get the maximum number of operations we keep in cache.
vips_cache_get_size ()
int
vips_cache_get_size (void
);
Get the current number of operations in cache.
vips_cache_get_max_mem ()
size_t
vips_cache_get_max_mem (void
);
Get the maximum amount of tracked memory we allow before we start dropping
cached operations. See vips_tracked_get_mem()
.
See also: vips_tracked_get_mem()
.
vips_cache_get_max_files ()
int
vips_cache_get_max_files (void
);
Get the maximum number of tracked files we allow before we start dropping
cached operations. See vips_tracked_get_files()
.
libvips only tracks file descriptors it allocates, it can't track ones
allocated by external libraries. If you use an operation like
vips_magickload()
, most of the descriptors it uses won't be included.
See also: vips_tracked_get_files()
.
vips_cache_set_max_files ()
void
vips_cache_set_max_files (int max_files
);
Set the maximum number of tracked files we allow before we start dropping
cached operations. See vips_tracked_get_files()
.
See also: vips_tracked_get_files()
.
vips_cache_set_dump ()
void
vips_cache_set_dump (gboolean dump
);
Handy for debugging. Print the operation cache to stdout just before exit.
See also: vips_cache_set_trace()
.
vips_cache_set_trace ()
void
vips_cache_set_trace (gboolean trace
);
Handy for debugging. Print operation cache actions to stdout as we run.
You can set the environment variable VIPS_TRACE
to turn this option on, or
use the command-line flag --vips-cache-trace
.
See also: vips_cache_set_dump()
.
vips_concurrency_set ()
void
vips_concurrency_set (int concurrency
);
Sets the number of worker threads that vips should use when running a VipsThreadPool.
The special value 0 means "default". In this case, the number of threads is set by the environment variable VIPS_CONCURRENCY, or if that is not set, the number of threads availble on the host machine.
See also: vips_concurrency_get()
.
vips_concurrency_get ()
int
vips_concurrency_get (void
);
Returns the number of worker threads that vips should use when running a VipsThreadPool.
vips gets this values from these sources in turn:
If vips_concurrency_set()
has been called, this value is used. The special
value 0 means "default". You can also use the command-line argument
"--vips-concurrency" to set this value.
If vips_concurrency_set()
has not been called and no command-line argument
was used, vips uses the value of the environment variable VIPS_CONCURRENCY,
If VIPS_CONCURRENCY has not been set, vips find the number of hardware threads that the host machine can run in parallel and uses that value.
The final value is clipped to the range 1 - 1024.
See also: vips_concurrency_get()
.
Types and Values
enum VipsOperationFlags
Flags we associate with an operation.
VIPS_OPERATION_SEQUENTIAL
means that the operation works like vips_conv()
:
it can process images top-to-bottom with only small non-local
references.
Every scan-line must be requested, you are not allowed to skip ahead, but as a special case, the very first request can be for a region not at the top of the image. In this case, the first part of the image will be read and discarded
Every scan-line must be requested, you are not allowed to skip ahead, but as a special case, the very first request can be for a region not at the top of the image. In this case, the first part of the image will be read and discarded
VIPS_OPERATION_NOCACHE
means that the operation must not be cached by
vips.
VIPS_OPERATION_DEPRECATED
means this is an old operation kept in vips for
compatibility only and should be hidden from users.
Signal Details
The “invalidate”
signal
void user_function (VipsOperation *vipsoperation, gpointer user_data)
Flags: Run Last