App framework blues
App framework blues
- Subject: App framework blues
- From: Erik Stainsby <email@hidden>
- Date: Tue, 14 Feb 2012 18:35:07 -0800
Hello list,
I'm still unclear about how to layout the project(s) for an own framework and app to use it.
So far I have tried two separate projects in the same workspace, as siblings, then including the framework in the app by dragging it in, either as a sub (inside the App project) or as a peer. No joy. Error messages about the framework depending upon itself.
Then I tried creating a second target within the app, a framework, and while that seemed to compile I got a similar error.
From the reading I've been doing this seems to be the tree I ought to be creating in a single workspace(?) is this:
-------------------------------
MyFramework (project)
MyApp
MyFramework.h
MyFramework.m
Supporting Files
Frameworks
Cocoa.framework
Other Frameworks
Products
MyFramework.framework
-------------------------------
MyApp (project)
MyApp
MyAppDelegate.h
MyAppDelegate.m
MainMenu.xib
Supporting Files
Frameworks
Cocoa.framework
Other Frameworks
Products
MyApp.app
-------------------------------
I understand from Chris Hanson that the framework should be built using the user setting:
DYLIB_INSTALL_NAME_BASE = @rpath
and the app which will include it should have:
LD_RUNPATH_SEARCH_PATHS = @executable_path/../Frameworks
which implies that the framework has to be copied into the Contents/Frameworks folder of the application, presumably as a step in the build of the application. However, any place in the application which I have tried to introduce teh framework causes a choke of some kind. I'm not getting this right and it is getting a bit frustrating.
Any clues, even to something I need to read up on, gratefully appreciated.
~ Erik
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden