On Oct 5, 2012, at 22:18 , Jerry Krinock <je...@ieee.org> wrote: > I know you can embed an Info.plist in a command-line tool, by specifying it > in the Info.plist Build Setting. But the only non-executable thing I've ever > seen embedded in a static library is a code signature.
A static library does not survive as such in an executable file. Unlike a framework, a static library is just a collection of unlinked object code. The linking process incorporates it into whatever is being linked. Thus the correct place for resource used by code in a static library is in the bundle of whatever it's linked into. If you add the static library itself to the project, you'd have to add its resources files manually. If you add the static library's own Xcode project to a workspace, I'd assume you normally would just specify the target inclusion for the resource files. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
