Plugin and standalone app in the same project?


#1

I would like to have a project that shares code between the standalone (Desktop/iOS) version, and the plugin version.

Eventually I’d like all the different targets to call the same components and processing functions, but each of the targets might also add a few behaviors that are unique to it (for example, the standalone version might generate it’s own playhead, or have a different menu).

Is there a way to do it in the Projucer without maintaining two different projects?
Ideally I’d like to be able to control the ‘shared’ resources from a central location.

Thanks!
Eyal


#2

The default plugin project will build a standalone + plugin versions with shared code.


#3

Can you add source files that will only compile/run on the stand alone app?

Also, can you deploy the standalone app as an iOS app (not as an AUv3 plugin)?


#4

Can you add source files that will only compile/run on the stand alone app?

I don’t think there’s a #define for standalones but you can check it programmatically.

Also, can you deploy the standalone app as an iOS app (not as an AUv3 plugin)?

Never done it but I believe so


#5

Actually, I think there is: JucePlugin_Build_Standalone