|
FrameworkDeployment
Using the framework in your appIf you're familiar with adding frameworks to a project in Xcode, skip to the last step below. If not, this is mostly pretty standard stuff that's in the documentation. You'll also need to read PopulatingTheView in order to actually display icons. Adding the framework in Xcode
/usr/bin/install_name_tool -change \
'@loader_path/../../../../../../../FileView.framework/Versions/A/FileView' \
'@executable_path/../Frameworks/FileView.framework/Versions/A/FileView' \
"${BUILT_PRODUCTS_DIR}/${EXECUTABLE_PATH}"That install_name_tool nastiness is required to make the framework 10.4 compatible, yet still work with the IB plugin. Using @rpath would be better, but it's only supported on 10.5. Using the IB pluginXcode seems to require that you add a reference to the compiled framework (typically Built Product relative path) in the "Linked Frameworks" group before it automagically finds the .ibplugin bundle inside the framework. Once you've compiled it and done that, open up one of your nibs in IB and you should see a "FileView" library item with two objects (FileView and FVColumnView). Sample ProjectTake a look at the FVIBPluginTest.xcodeproj sample project, which demonstrates all of the points made here. |