Bundling and Installing a Plug-in
The easiest way to build a new FxPlug plug-in is to create a New Project in Xcode and use one of the FxPlug
templates in the Standard Apple-Plug-ins category: FxPlug Filter, FxPlug Generator, or FxPlug Transition.
For examples of complete FxPlug plug-ins, see the directory /Developer/Examples/FxPlug.
Note: To avoid plug-in conflicts,you must edit the UUID entries in the Info.plistfile.You can create
unique UUIDs by issuing the uuidgen command in the Terminal application. (See the “Frequently Asked
Questions” section below for details on using uuidgen.)
Two Mac OS X folders are reserved for FxPlug installation. When scanning for plug-ins, host applications
recursively search the folder hierarchy from these locations:
/Library/Plug-Ins/FxPlug/
~/Library/Plug-Ins/FxPlug/
As you develop your plug-in and test it with the host application, you may find it convenient to perform the
installation via a Copy Files build phase. Alternatively, you can create a symbolic link inside
/Library/Plug-Ins/FxPlug/, pointing to the build-product directory specified in Xcode’s Project
Preferences. Depending on your settings, you can create the symbolic link in the Terminal application like
this: