| Crates.io | clap-wrapper |
| lib.rs | clap-wrapper |
| version | 0.2.1 |
| created_at | 2025-06-09 18:13:48.388661+00 |
| updated_at | 2026-01-11 19:23:12.335326+00 |
| description | An easy way to use clap-wrapper in your audio plugins! |
| homepage | |
| repository | https://github.com/blepfx/clap-wrapper-rs |
| max_upload_size | |
| id | 1706244 |
| size | 4,533,551 |
An easy way to use clap-wrapper in your Rust plugins!
cmake. Instead it uses the cc crate to compile the clap-wrapper code.clap_entry exports multiple plugins,
only the first one will be exported.Add this to your Cargo.toml:
[dependencies]
clap-wrapper = { version = "0.2.0", features = ["vst3", "auv2", "parallel"] } # these features are enabled by default
Then, in your lib.rs:
// exports `GetPluginFactoryAUV2` symbol.
clap_wrapper::export_auv2!();
// exports `GetPluginFactory` symbol and extra VST3 symbols.
clap_wrapper::export_vst3!();
This will export VST3 and AUv2 entrypoints that use the clap_entry symbol exported from your crate (as an example, nih_plug::nih_export_clap exports it).
Keep in mind, that clap-wrapper-rs only adds the necessary entrypoints that reexport the CLAP plugin you already have. You'd still have to use a crate like nih-plug to actually create the plugin.
After building, you have to manually "bundle" your plugin. This means setting up the correct directory structure and copying the necessary files. See VST 3 Developer Portal: Plug-in Format Structure for more info about VST3 directory structure. For AUv2, the directory structure is similar.
Note that when building for MacOS you have to add a Info.plist file yourself.
Check out Info.vst3.plist and Info.auv2.plist for an example of what Info.plist should look like.
See validate.yml for a complete example of how to build, bundle and validate a plugin.
vst3 and auv2 features to enable/disable building those wrappers.clap-wrapper to latest.Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.