...
- If the new plugin will be part of the default set, open OpenEphys.xcworkspace. Otherwise, just open Xcode.
- Select File->New->Project. In the dialog that pops up, choose macOS->Framework & Library->Bundle, and click Next. Give your product a name (e.g. "ExampleProcessor"), then click Next. A file selection dialog will pop up, allowing you to choose where the new project is created. For non-default plugins, any location is fine. Projects for default plugins should go in Builds/MacOSX/Plugins; also, in the "Add to" pop-up menu, select the OpenEphys workspace, then, in the "Group" menu that appears, select "Plugins". Click Create, and Xcode should open the new project.
- Select File->Add Files to "<your project name>" to add source files to the project. Click the Options button, and in the "Add to targets" section, uncheck all targets. This will ensure that the files are referenced, not copied. Then, click Add.
The next steps depend on whether the project is for a default plugin (included in the plugin-GUI source tree) or not.
...
- Go to File->Add Files to "<your project name>", and select the files Plugin_Debug.xcconfig and Plugin_Release.xcconfig in the Config folder. Click Click the Options button, and in the "Add to targets" section, uncheck all targets. ThenThen, click Add.
- Select the project file in Xcode, and navigate to the top-level "Info" panel for the project. In the "Configurations" section, expand Debug and Release, and select the appropriate configuration file for each configuration (Plugin_Debug for Debug, Plugin_Release for Release).
- Navigate to the project-level build settings. Select "All" and "Levels". Then, select all settings in the list, and press delete. Once this is done, the column for project-level settings should be empty.
- Navigate to the target-level build settings. Delete all settings except "Info.plist File", "Product Bundler Identifier", and "Product Name".
- (Optional) Add plugin-specific build settings (e.g. paths to external libraries) as needed.
...