• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

doc/H03-May-2022-4,9944,077

lv2/H03-May-2022-16,04810,716

lv2specgen/H03-May-2022-8,5025,199

plugins/H03-May-2022-5,8654,053

resources/logo/H03-May-2022-588586

schemas.lv2/H03-May-2022-3,2942,900

util/H03-May-2022-112107

waflib/H03-May-2022-44,62235,321

.clang-tidyH A D02-Jan-2021606 2221

.gitlab-ci.ymlH A D19-Aug-20203.1 KiB157121

.gitmodulesH A D09-Feb-202070 43

COPYINGH A D21-Apr-2019846 1713

NEWSH A D07-Jan-202111.5 KiB269236

README.mdH A D21-Apr-20192.2 KiB8350

lv2.pc.inH A D21-Apr-2019145 86

wafH A D28-Mar-2020709 2817

wscriptH A D07-Jan-202129.4 KiB828633

README.md

1LV2
2===
3
4LV2 is a plugin standard for audio systems. It defines a minimal yet extensible
5C API for plugin code and a format for plugin "bundles".  See
6<http://lv2plug.in> for more information.
7
8This package contains specifications (C headers and Turtle files),
9documentation generation tools, and example plugins.
10
11Building and installation requires only Python 2.6.  Building the documentation
12requires Doxygen.
13
14
15Installation
16------------
17
18A typical build looks something like this:
19
20    ./waf configure --prefix=/foo
21    ./waf
22    sudo ./waf install
23
24or, for packaging:
25
26    DESTDIR=/home/packager/lv2root ./waf install
27
28For help on the other available options, run:
29
30    ./waf --help
31
32The bundle installation directory can be set with the --lv2dir option, e.g.:
33
34    ./waf configure --lv2dir=/foo/lib/lv2
35
36Configuring with `--lv2-user` will install bundles to the user-local location.
37
38
39Packaging
40---------
41
42Specification bundles are both a build-time and run-time dependency of programs
43that use LV2.  Programs expect their data to be available somewhere in
44`LV2_PATH`.
45
46See <http://lv2plug.in/pages/filesystem-hierarchy-standard.html> for details on
47the standard installation paths.
48
49Do not split up LV2 bundles, they are self-contained and must remain whole.
50Other than that, things may be split to suit distribution needs.  For example,
51separate packages for specifications, tools, and plugins, may be good idea.
52
53
54Header Installation
55-------------------
56
57By default symbolic links to headers in bundles are installed to `INCLUDEDIR`.
58If symbolic links are a problem, configure with `--copy-headers` and copies
59will be installed instead.
60
61Headers are installed in two paths, the universal URI-based style:
62
63    #include "lv2/lv2plug.in/ns/ext/urid/urid.h"
64
65and the newer simple core style:
66
67    #include "lv2/urid/urid.h"
68
69Projects are encouraged to migrate to the latter style, though note that this
70style of include path may only be used by official LV2 specifications.
71
72
73Documentation
74-------------
75
76Configuring with the --docs option will build the documentation for all the
77included specifications if Doxygen is available.  For example:
78
79    ./waf configure --docs
80    ./waf
81
82Specification documentation is also availabe online at <http://lv2plug.in/ns>.
83