LV2LINT(1)

💅 lv2lint: the LV2 lintian bestie 💅

Okay so this is the manual page for lv2lint — yes, LV2LINT(1) in the General Commands Manual — and it’s giving “your plugin’s strictest friend who still wants you to slay.” 🦋

🌸 NAME 🌸

lv2lint — an LV2 lintian. 💖

✨ SYNOPSIS ✨

lv2lint [OPTIONS] {PLUGIN_URI}*

🎀 DESCRIPTION 🎀

So here’s the vibe: lv2lint checks whether the LV2 plugins you give it are actually up to the specification. ✅

It doesn’t only check the *.ttl — it literally loads the plugins (and their UIs) and checks whether the required features and exposed extensions actually match between the binary and the *.ttl. 👀

That means it finds errors that cannot readily be found by just checking the *.ttl for validity. Iconic, honestly.

Bestie, it is good practice to run it over your plugins as part of your continuous integration — after checking them for validity with sord_validate and before releasing them to the public. 🫶

💅 OPTIONS 💅

No flags left behind, no cap. ✨

• -v — print version and license information. 💖
• -h — print usage information. ✨
• -q — quiet mode, show only a summary. 🤫
• -d — show verbose test item documentation. 📚
• -o — run online test items. 🌐
• -m — create mail to plugin author. 📧
• -g GREETER — custom mail greeter. 👋
• -s SYMBOL_PATTERN — symbol pattern (shell wildcard) to whitelist (can be used multiple times). 🧵
• -l LIBRARY_PATTERN — library pattern (shell wildcard) to whitelist (can be used multiple times). 📚
• -u URI_PATTERN — URI pattern (shell wildcards) to be prefixed to test, symbol and library whitelist patterns (can be used multiple times). The latter whitelist pattern will then only be effective when also the current URI pattern matches (e.g. for plugin itself or one of its UIs). 🔗
• -t TEST_PATTERN — test name pattern (shell wildcards) to whitelist (can be used multiple times). ✅
• -I INCLUDE_DIR — apart from default LV2 plugin install paths, use include directory to search for plugins (can be used multiple times). 📁
• -M (no)pack (Default: pack) — modes to enable/disable, e.g. (pack)ager mode skips some fatal tests for distribution packagers that are important only for freely distributed binaries. If you are a distribution packager, preferebly run with '-M pack' (Default). If you want to build binaries for distributing, preferably run with -M nopack. 📦
• -S (no)warn|note|pass|all (Default: fail|warn) — apart from errors alone (fail), also show warnings (warn), notes (note), passes (pass) or all (all) on console. The no- prefix inverts the meaning. 🖥️
• -E (no)warn|note|all (Default: fail) — apart from errors alone (fail), also treat warnings (warn), notes (note) or all (all) as errors. The no- prefix inverts the meaning. 🚨

🎨 LICENSE 🎨

Artistic License 2.0. 📜

👑 AUTHOR 👑

Hanspeter Portner (dev@open-music-kontrollers.ch). 💌

🦋 SEE ALSO 🦋

sord_validate(1) — go give it a look too, bestie. 💜

That’s the whole page, bestie — from the General Commands Manual, page LV2LINT(1), dated Jan 15, 2021. Mwah! 💖