File: README.md

package info (click to toggle)
lv2 1.14.0~dfsg1-2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 2,532 kB
  • sloc: python: 16,370; ansic: 4,992; xml: 182; sh: 76; makefile: 45
file content (76 lines) | stat: -rw-r--r-- 2,099 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
LV2
===

LV2 is a plugin standard for audio systems. It defines a minimal yet extensible
C API for plugin code and a format for plugin "bundles".  See
<http://lv2plug.in> for more information.

This package contains specifications (C headers and Turtle files),
documentation generation tools, and example plugins.

Building and installation requires only Python 2.6.  Building the documentation
requires Doxygen.


Installation
------------

A typical build looks something like this:

    ./waf configure --prefix=/foo
    ./waf
    sudo ./waf install

or, for packaging:

    DESTDIR=/home/packager/lv2root ./waf install

For help on the other available options, run:

    ./waf --help

The bundle installation directory can be set with the --lv2dir option, e.g.:

    ./waf configure --lv2dir=/foo/lib/lv2

Configuring with `--lv2-user` will install bundles to the user-local location.


Packaging
---------

Specification bundles are both a build-time and run-time dependency of programs
that use LV2.  Programs expect their data to be available somewhere in
`LV2_PATH`.

See <http://lv2plug.in/pages/filesystem-hierarchy-standard.html> for details on
the standard installation paths.

Do not split up LV2 bundles, they are self-contained and must remain whole.
Other than that, things may be split to suit distribution needs.  For example,
separate packages for specifications, tools, and plugins, may be good idea.


Header Installation
-------------------

By default symbolic links to headers in bundles are installed to `INCLUDEDIR`.
If symbolic links are a problem, configure with `--copy-headers` and copies
will be installed instead.

Note that include paths relative to `PREFIX` may not be changed, since projects
using LV2 use include paths like:

    #include "lv2/lv2plug.in/ns/ext/urid/urid.h"


Documentation
-------------

Configuring with the --docs option will build the documentation for all the
included specifications if Doxygen is available.  For example:

    ./waf configure --docs
    ./waf

Specification documentation is also availabe online at <http://lv2plug.in/ns>.