This avoids warnings about potential null pointer dereferences, which is true, but in this case the buffer are static so it's really a programming error if there is ever an overrun.
|2 years ago|
|doc||3 years ago|
|lv2||2 years ago|
|lv2specgen||3 years ago|
|plugins||2 years ago|
|resources/logo||3 years ago|
|schemas.lv2||4 years ago|
|util||3 years ago|
|waflib@6321098e6b||3 years ago|
|.clang-tidy||2 years ago|
|.gitignore||3 years ago|
|.gitlab-ci.yml||3 years ago|
|.gitmodules||4 years ago|
|COPYING||11 years ago|
|README.md||5 years ago|
|lv2.pc.in||11 years ago|
|waf||3 years ago|
|wscript||3 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 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.
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:
The bundle installation directory can be set with the --lv2dir option, e.g.:
./waf configure --lv2dir=/foo/lib/lv2
--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
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.
By default symbolic links to headers in bundles are installed to
If symbolic links are a problem, configure with
--copy-headers and copies
will be installed instead.
Headers are installed in two paths, the universal URI-based style:
and the newer simple core style:
Projects are encouraged to migrate to the latter style, though note that this style of include path may only be used by official LV2 specifications.
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.