[jcelerier]

I had looked into it ! but it seemed that making a DPF plug-in involved a lot of boilerplate, while I really wanted to do something where I can just include a couple headers and get going, without any particular compilation hassle (the whole library is header-only as it is pretty much entirely templates).

[gavinray]

This is the absolute worst part of VST3. These 2 soul-crushing lines in the build file:

https://github.com/steinbergmedia/vst3_pluginterfaces/blob/m...

  # pluginterfaces should actually be a header-only library,
  # but it has some sources as well which need compilation.

Should theoretically be fixable right, so that it's purely the interfaces and doesn't need compilation? Why on earth did they do it like this?...

[spacechild1]

Actually, you can write VST3 plugins/hosts using only the header files in pluginterfaces. (I needed to do this because the source files didn't even compile with MinGW. Maybe they have fixed this.) I don't use a single VST3 source file in my “vstplugin“ project: https://git.iem.at/pd/vstplugin

[gavinray]

This is very useful to know -- TIL, thank you!!

[jcelerier]

Yeah, until now I had resigned myself to linking against stmg_common in cmake. But maybe they can be split out to simplify that whole... Thing. I almost have it working, will push tomorrow after some sleep and then will add vcpkg as you showed :)

[gavinray]

  > "I almost have it working, will push tomorrow after some sleep and then will add vcpkg as you showed :)"

Bless, the hero we needed but didn't deserve