LV2 subproject with meson
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
David Robillard 770af26981 Clean up external vocabularies. 8 years ago
doc Fix too long prototype lines in Doxygen. 8 years ago
lv2/ Use lowercase for time property labels. 8 years ago
lv2specgen Add link to spec index on spec pages. 9 years ago
plugins Add missing include. 8 years ago
schemas.lv2 Clean up external vocabularies. 8 years ago
COPYING Remove individual extension pkg-config files and build scripts. 11 years ago Update README and fix broken link. 9 years ago Add pkgconfig file for all of LV2. 11 years ago
waf Upgrade to r100/autowaf. 8 years ago
wscript Install schema bundle for host/utility support. 8 years ago


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 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.


A typical build looks something like this:

./waf configure --prefix=/foo
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.


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 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/"


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

./waf configure --docs

Specification documentation is also availabe online at