|
I’m working on wrapping my head around the new FxPlug 3.x paradigms. Sorry if it should be obvious to me, but I’m still uncertain on issues around the build products.
I’ve come to these tentative conclusions. Please correct me if I’m wrong:
* The base fxplug filter template has three targets and schemes: Wrapper Application, XPC Service, and Plugin. All three will be generated when building — it doesn’t matter which particular target you have selected in Xcode.
* The source files we author need to be a member of the Plugin target (rather than the Wrapper Application and XPC Service targets) in order for them to be found and included appropriately. (Due to the fact that the source I am writing is really only part
of the plugin, which is then wrapped in the XPC bundle which is then wrapped in the App.)
* Despite the fact that Xcode generates separate .app, .fxplug folder, and .pluginkit products in the Build folder, the only one that really “matters” to me in the end is the .app, which in theory is capable of standing alone, without the other two .fxplug
and .pluginkit products.
Thanks,
----
Dr Bret Battey
Reader in Music, Technology and Innovation
De Monfort University
|