In terms of what folder to put code in, this release note should be somewhat helpful:For example if we were calling a Mac binary, what code folder would be required?
https://github.com/montegoulding/liveco ... support.md
(and the platform ID document it leads to).
For Mac dylibs, you'd want them in /code/universal-mac/
CorrectWhen calling parts of the Mac or iOS framework we do not actually need a code folder I guess.
You should only need to put the binary in the right place and load the extension using the extension builder - everything else is handled by the IDE.When calling any binary how do we signal to lc that this or that code binary is required.