source: roaraudio/doc/man1/roarpluginrunner.1 @ 5496:855840432b9a

Last change on this file since 5496:855840432b9a was 5496:855840432b9a, checked in by phi, 12 years ago

added manpage for roarpluginrunner(1)

File size: 2.8 KB
Line 
1.\" roarpluginrunner.1:
2
3.TH "roarpluginrunner" "1" "FIXME(DATE)" "RoarAudio" "System User's Manual: roarpluginrunner"
4
5.SH NAME
6
7roarpluginrunner \- Run RoarAudio plugins
8
9.SH SYNOPSIS
10
11roarpluginrunner [OPTIONS]... PLUGIN
12
13.SH DESCRIPTION
14
15This tool can be used to run RoarAudio plugins or report information about the plugin.
16roarpluginrunner loads the plugins in a plugin container with the given parameters passed.
17This allows you to run all universal plugins as well as some other plugins out side
18a specific host. It can also be used for Testing the plugins.
19
20There are three modes of operation: Running, Running as application and Explaining.
21The first mode (Running) is what most host applications will do.
22Running as application is different in the way that all parameters left on the command line
23after the plugin name are parsed and passed to the plugin as plugin arguments.
24
25In this mode parameters passed after the plugin name are splitted into key-value-pairs.
26An option (beginning with two dashes) are passed as pair with the option name (the dashes) removed as key
27and no value. If it contains a equality sign the part after it is passed as value.
28Options with a single dash are splitted each letter into an own key-value-pair with only the key set.
29Non-option arguments (with no dashes) are passed as value-only pairs.
30After a pure double dash all parameters are passed as non-options with the double dash completely removed
31from the key-value-array.
32
33In the explain mode the plugin is loaded but not run. The meta information about the plugin are reported.
34This includes true meta data like the name, authors and copyright but also technical meta data
35like the host application's name the plugin is written for.
36
37When the plugin uses symbols from the host directly the plugin may not be loaded into roarpluginrunner
38because of the system's library loader limits. On GNU/Linux (and other POSIX like implementations)
39this is only true if the plugin uses global variables of the host. Plugins using functions of the host
40can still be loaded in this mode.
41
42.SH "OPTIONS"
43
44.TP
45\fB-h \-\-help\fR
46Prints a help message.
47
48.TP
49\fB-v \-\-verbose\fR
50Be verbose. Can be used multiple times.
51
52.TP
53\fB--server SERVER\fR
54Set default server to SERVER.
55
56.TP
57\fB--run\fR
58Run plugin.
59
60.TP
61\fB--run-as-application\fR
62Same as \-\-run except all tailing arguments are passed to the plugin.
63This is also used by \fBroarpluginapplication\fR(1).
64
65.TP
66\fB--explain\fR
67Explain plugin. This lists all details about the plugin without actually running it.
68
69.TP
70\fB--appname NAME\fR
71Sets the appname.
72
73.TP
74\fB--abiversion ABI\fR
75Set the ABI version.
76
77.TP
78\fB--args ARGS\fR
79Set plugin arguments.
80
81.SH "SEE ALSO"
82\fBroarpluginapplication\fR(1),
83\fBroartips\fR(7),
84\fBlibroar\fR(7),
85\fBRoarAudio\fR(7).
86
87.SH "HISTORY"
88
89For history information see \fBRoarAudio\fR(7).
90
91.\" ll
Note: See TracBrowser for help on using the repository browser.