Re: Building an agent app into another app's bundle
Re: Building an agent app into another app's bundle
- Subject: Re: Building an agent app into another app's bundle
- From: Jens Miltner <email@hidden>
- Date: Mon, 09 Mar 2009 12:16:41 +0100
Am 06.03.2009 um 04:41 schrieb Chris Espinosa:
On Mar 5, 2009, at 7:17 PM, Rick Mann wrote:
I have a Cocoa app (call it "U") that provides a UI for a user
agent Cocoa app (call it "A"). I have two projects, one for each
app. I'd like to set up Xcode so that when I build the UI app
("U"), it builds the agent app ("A"), and then (a copy of) A.app
should end up inside U.app's bundle.
How do I set up Xcode to do this? If this is already documented,
can someone point me to it?
1) Drag project A into project U. This creates a cross-project
reference from U to A, and makes A's targets and build products
available to U.
2) In project U, drag A's target into the target for U. That
creates a project dependency: when you build U, it makes sure A is
up to date.
3) Still in project U, drag A's build product (A.app) into the Copy
Bundle Resources build phase for target U. That causes A.app to be
copied into U.app/Contents/Resources when U is built.
Although you probably really want to create a custom copy files build
phase and make it copy A.app into U.app's Executables folder
("Contents/MacOS") which is - AFAICK - the suggested location for
auxiliary executables, not the resources directory. This becomes
important if you should ever decide to code-sign your executable...
</jum>
_______________________________________________
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