LV2: modul zesilovače, dle oficiálního příkladu, ale bez závislosti na Pythonu – stačí gcc a make
1 # LV2 plugins are installed in a ``bundle'', a directory with a standard
2 # structure. Each bundle has a Turtle file named `manifest.ttl` which lists
3 # the contents of the bundle.
5 # Hosts typically read the manifest of every installed bundle to discover
6 # plugins on start-up, so it should be as small as possible for performance
7 # reasons. Details that are only useful if the host chooses to load the plugin
8 # are stored in other files and linked to from `manifest.ttl`.
12 # LV2 makes use of URIs as globally-unique identifiers for resources. For
13 # example, the ID of the plugin described here is
14 # `<http://lv2plug.in/plugins/eg-amp>`. Note that URIs are only used as
15 # identifiers and don't necessarily imply that something can be accessed at
16 # that address on the web (though that may be the case).
18 # ==== Namespace Prefixes ====
20 # Turtle files contain many URIs, but prefixes can be defined to improve
21 # readability. For example, with the `lv2:` prefix below, `lv2:Plugin` can be
22 # written instead of `<http://lv2plug.in/ns/lv2core#Plugin>`.
24 @prefix lv2: <http://lv2plug.in/ns/lv2core#> .
25 @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
27 # ==== Describing a Plugin ====
29 # Turtle files contain a set of ``statements'' which describe resources.
30 # This file contains 3 statements:
32 # |================================================================
33 # | Subject | Predicate | Object
34 # | <http://lv2plug.in/plugins/eg-amp> | a | lv2:Plugin
35 # | <http://lv2plug.in/plugins/eg-amp> | lv2:binary | <amp.so>
36 # | <http://lv2plug.in/plugins/eg-amp> | rdfs:seeAlso | <amp.ttl>
37 # |================================================================
39 # Firstly, `<http://lv2plug.in/plugins/eg-amp>` is an LV2 plugin:
40 <http://lv2plug.in/plugins/eg-amp> a lv2:Plugin .
42 # The predicate ```a`'' is a Turtle shorthand for `rdf:type`.
44 # The binary of that plugin can be found at `<amp.ext>`:
45 <http://lv2plug.in/plugins/eg-amp> lv2:binary <amp.so> .
47 # This file is a template; the token `@LIB_EXT@` is replaced by the build
48 # system with the appropriate extension for the current platform before
49 # installation. For example, in the output `manifest.ttl`, the binary would be
50 # listed as `<amp.so>`. Relative URIs in manifests are relative to the bundle
51 # directory, so this refers to a binary with the given name in the same
52 # directory as this manifest.
54 # Finally, more information about this plugin can be found in `<amp.ttl>`:
55 <http://lv2plug.in/plugins/eg-amp> rdfs:seeAlso <amp.ttl> .
57 # ==== Abbreviation ====
59 # This file shows these statements individually for instructive purposes, but
60 # the subject `<http://lv2plug.in/plugins/eg-amp>` is repetitive. Turtle
61 # allows the semicolon to be used as a delimiter that repeats the previous
62 # subject. For example, this manifest would more realistically be written like
65 <http://lv2plug.in/plugins/eg-amp>
68 rdfs:seeAlso <amp.ttl> .