As a starting point, I recommend to clone the above repo, switch to its linux branch, and try to build the IPlugInstrument example using cmake.
Have a look at its CMakeLists.txt file, towards the bottom you’ll see a call to iplug_setup_plugin that includes a parameter specifying what plugin formats to build.
I recommend changing that to app first to only build the standalone app, or it will give you plenty of errors due to missing SDKs etc for some formats.
You’ll also need to have a few packages installed to be able to build. Have a look at this post: Linux support or iPlug2 - #2 by olilarkin
It’s an old post but helped get me started. There are probably more but I can’t remember, but it can be figured out from the error messages you’ll get when building.
To set up the cmake build, I run cmake -S . -B build-linux. For my own project that sits outside the repository, I’m also adding the -DIPLUG2_SDK_PATH=/home/youruser/path_to_iplug2 option to point it the right way.
If that succeeds, I run cmake --build build-linux to actually build.
I think that was enough to get the IPlugInstrument standalone app to run at least.
Once that works, you should be able to replace its code with your own.
Perhaps you’re more interested in effects plugins .. in that case you’ll probably have to copy the CMakeLists.txt from the IPlugInstrument and modify it as needed, because other example projects seem to still use an out-of-date setup in theirs .. I’ve been able to create an effects plugin doing so, changing channel-io to 2-2 and category to audio-effect
Building clap and vst3 mostly works the same way after adding the respective SDKs just like you would on win or mac.
Once you manage to build and run, you’ll probably encounter some UI issues and crashes. A lot of it is due to unfinished linux code in the framework. I spent a lot of effort there already and it would be a pity if you’d have to do it on your own again .. let me see if I can find some time to get my code uploaded, perhaps early next year!