Age | Commit message (Collapse) | Author | Files | Lines |
|
These are required by OWL tools to use vocabulary from another ontology.
Though we don't use OWL tools in LV2, they are at least useful for sanity
checking the semantic side of things. These properties are also nice to have
anyway, since they clearly describe the dependencies between specifications.
|
|
|
|
|
|
For consistency, and because clang-tidy can't figure out if a define is an
include guard unless it ends the file.
|
|
|
|
|
|
These are included in the manifest so that hosts can discover them. Having
them in the data file as well is redundant, and in some cases requires an
otherwise unnecessary import of the core spec.
|
|
|
|
Towards putting more here than just the project metadata, and is a bit cleaner
of a naming scheme anyway.
|
|
This makes it feasible to merge the LV2 documentation into more broad
documentation in a meta-project.
|
|
These are not necessary since they are not recursive types, and the names
violated the C standard. There also seems to be a bug in Doxygen where
TYPEDEF_HIDES_STRUCT was not working, which made the documentation confusing
and ugly.
Strictly speaking, this could break user code that used these names directly,
but this was never intended to be supported and should be fixed if it actually
occurs anywhere.
|
|
|
|
This removes all the extra bundle content from the documentation output and
instead makes pages directly at the URI of specifications. This way, links to
fragments in spec pages (which are often copy and pasted) are correct fragment
identifiers like <http://lv2plug.in/ns/lv2core#Plugin> instead of
<http://lv2plug.in/ns/lv2core/#Plugin>.
|
|
|