Re: Re-"Targeting" to build a bundle
Re: Re-"Targeting" to build a bundle
- Subject: Re: Re-"Targeting" to build a bundle
- From: Fritz Anderson <email@hidden>
- Date: Thu, 30 Apr 2009 11:47:28 -0500
On 30 Apr 2009, at 11:07 AM, Thomas Engelmeier wrote:
I tried to change a (copied) target to build a bundle instead of a
plain dylib. I played extensively with the target settings (copying
one-by-one from a test bundle project) but I still get a "plain"
dylib without a bundle container. Also, the Target info dialog for
the test bundle has an additional Info.plist tab while the former
dylib one has not.
The setup / list of contained files is pretty complex so I'd prefer
not to create a new target from scratch and add all 450 files one-by
one. Is there anything that helps that process short of changing the
dylib target into a static lib one and then linking it to a dummy
file in a new bundle target?
The Xcode build system works by knowing what the endpoint of the build
is. All the build rules are inferred from that plus the types of the
files that are the ultimate inputs to the process. You can influence
the handling of the files at the input end, by moving them among build
phases, but you can't change the output end. You have to create a new
target for the bundle.
Create the new target.
Use the Groups & Files list to select all the source files for the
dylib, such as by selecting the group (I hope you have one) that
encloses them.
Get Info (cmd-I). Show the Targets tab.
Check the new target.
All the files now belong to the new target.
— F
--
Fritz Anderson -- Xcode 3 Unleashed: Now in its second printing -- <http://x3u.manoverboard.org/
>
_______________________________________________
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