Age | Commit message (Collapse) | Author | Files | Lines |
|
This allows the LV2 source distribution to be used as an include path for
compilers and an LV2_PATH for applications, at the expense of self-contained
bundles. That's a nice idea, but it made LV2 itself weird and annoying to
depend on. This rearranges things so that directories in the source tree
correspond more closely to installation directories.
To make this possible, the "aux" directory in the documentation output has been
changed to "style", to avoid the reserved name "aux" on Windows.
|
|
|
|
|
|
|
|
|
|
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.
|
|
Similar to the previous commit, this was non-standard and caused documentation
issues. With this commit, the data structures index page looks as expected.
Unlike the previous commit, though, these names are actually needed because the
struct definition refers to itself. Simply use the same name instead of the
underscore prefix, since the "struct namespace" in C is different anyway.
|
|
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 order is better because it ensures that headers can stand alone and
include everything they need. Several missing includes were exposed by this,
and are also fixed in this commit.
|
|
|
|
|