(1) βClean allβ your projects so that there is no detritus during the execution.
(2) Install Xcode to use the general assembly products directory (I bind my / tmp / so that it periodically resets). Preference is given to the "Construction" section.
(3) Rebuild OsiriX (so that it is built into the shared folder).
(4) Make sure that the active configuration of your plug-in project has the same name as the configuration in OsiriX that you created (3). (This should probably be "Debug" or "Release", depending on what you are creating). Configurations can be edited in the assembly settings editor.
(5) Create your plugin.
(6) Add the custom executable to your plug-in project and set the path to OsiriX (Project -> New Custom Executable ...).
Now you can create and run or build and debug your project. He will launch OsiriX from the product catalog for the assembly. You may also want to install OsiriX to search for packages in your build product catalog, if not already. Or you can create a symbolic link from one of the catalogs of OsiriX plug-ins into a package in your product catalog.
cd /path/to/OsiriX's/bundle/directory ln -s /path/to/build/products/YourPlugin.bundle
This is a very standard way to create Xcode for plugin development. For example, the developers of the preferences panel will configure their own executable file for SystemPreferences.app (even in / Applications - there is no need to point to the "debug" assembly of the application).
source share