Closed andreij closed 7 months ago
Hi @andreij
Yes indeed, I need to support this. That's going to be a breaking change and not really happy about it. Didn't find time yet to work on it and to find a satisfactory solution, but I will.
Initially, as you noted, Rack didn't support arm64
even though it was there already for quite some time.
When they wanted to add support to it, they went to change the path to the plug-in to include the architecture. They had an approach to use the library extension (dylib, dll, so) to imply the architecture and of course that was going to fail at some point.
In your case, a workaround in the meantime could be to run VCV Rack with Rosetta, and make sure the plug-in module is in the x86_64
variant of the plug-ins folder.
Thanks for your suggestion and thanks again for the wonderful platform you put in place!
(I reopen the issue in order to track it over time)
I'm running VCV Free Rack 2.4.1 https://github.com/VCVRack/Rack/blob/v2/CHANGELOG.md#241-2023-08-24 on a MacOs M2 (Sonoma).
I've followed the Ebb installation guide, and setup using:
Then in
samples/drop
module:After that I run Simulation in VSCode, which copies the Plugin to the
Rack2/plugins
which seems apparently ignored by Rack startup, since the plugin name doesn't appear in log.txt. I quickly went through code and it's supposed to move plugins from that old directory to the new formatRack2/plugins-XXX-YYY
but it doesn't seem so.I've tried to manually move the
Drop
plugin to the new plugins directory and I get this error:I'm not an expert of compilers, so I've went through the Make process and the
x86
architecture is hardcode (I've tried to switch flags to ARM but ended in a rabbit hole) so it seems I'm missing some steps to how I'm supposed to configure Erbb for my machine?I really love the framework you setup, so I hope to help to have this fixed, if possible.