I thought I’d start a thread to link development builds of plugins that “should” work with V2. Post in the comments and I will add to this top post and then probably delete comments unless they add to the discussion in other ways. Devs feel free to add your own beta builds here, and feel free to mark them as a beta or alpha if you want feedback or want people to be aware that you know there probably are bugs still to be ironed out.
buyer beware - building does not mean fully working or without bugs - your mileage may and probably will vary. This is the thread for bleeding edges.
PSA if there is a plugin you are waiting for - in my experience so far at least - Andrew’s view that many plugins can be updated by changing version in plugin.json to 2.0.0 and make clean and make dist is proving to be true.
I don’t see a single plugin build here that specifies the Rack version number that it was built against. That’s a sure way to create massive confusion before the ABI is stable. EDIT: Actually DanTModules does. Follow his example, or mine. Rack development blog - #70 by Vortico
This was built against Rack 2 Community Edition Rack 2.git.5c47e6e0, NOT the posted beta so won’t work there but builds fine after version number bump in pluginb.json
Also posted the Parasites v2 Windows port and as the main southpole one they do not work on the windows official beta but work fine on my local Rack v2 build from today…
Great, thanks. However, that binary doesn’t seem to work with Rack-2.git.b04e4117-win. The southpole folder is created but no modules appear in the browser. Did you build it from your own build of Rack2?
[0.354 info src/plugin.cpp:108 loadPlugin] Loading plugin from C:/Users/paul/Documents/Rack2/plugins/southpole
[0.354 warn src/plugin.cpp:161 loadPlugin] Could not load plugin C:/Users/paul/Documents/Rack2/plugins/southpole: Failed to load library C:/Users/paul/Documents/Rack2/plugins/southpole/plugin.dll: code 127
HHmmmm, you are correct, however I do not even get an error on the posted beta version, so looks like that needs a new build against current v2 source to work. So can’t fix that sadly, but should work on later v2 builds (at least current level). Works fine on my today v2 local Rack build…
Miy local Rack v2 build reports to be ‘Rack Community Edition2.git5c47e6e0’