clap VS dlfcn-win32

For CLAP plugins, hopefully this extension will land at some point, and host and plugin developers will implement support for it. https://github.com/free-audio/clap/pull/311

In the previous release, which came out a few days before this one, I got the GUI to run in Bitwig on Windows. It unfortunately doesn't yet work on macOS. I also implemented a new patch format which has better support for compatibility transformations and the clap state extension. Patches created with previous versions are automatically converted when opened.

If you need inspiration from a well designed C plugin API, look at CLAP.

I'm proud to announce the latest major yabridge release. I spent the last couple months working on support for bridging CLAP plugins. With yabridge 5.0 you can now use Windows CLAP plugins in native Linux CLAP hosts with full functionality. CLAP is a collaborative effort by a group of plugin and host developers of all backgrounds to create a permissively licensed extensible plugin standard that is simple while also catering to the needs of plugin developers, host developers, and musicians alike. When bridged under yabridge, these plugins are likely to have lower bridging overhead than their VST2 and VST3 counterparts while also being more responsive and offering better support for instrument plugins and parameter modulation.

Maybe make a CLAP version?

GitHub

When trying to configure and build ign-common (second step 3.), a required dependency is dlfcn-win32.cmake. This isn't mentioned in the instructions as something to install, so I just grabbed it from https://github.com/dlfcn-win32/dlfcn-win32. However, dlfcn-win32-config.cmake comes as an .in file ("dlfcn-win32-config.cmake.in"). Removing the ".in" extension just makes it unreadable when configuring ign-common. How do I properly install the module for ign-cmake?