Re: CodeSign Warning when building static lib target for iPhone on XCode 3.1
Re: CodeSign Warning when building static lib target for iPhone on XCode 3.1
- Subject: Re: CodeSign Warning when building static lib target for iPhone on XCode 3.1
- From: Fritz Anderson <email@hidden>
- Date: Fri, 24 Oct 2008 13:32:30 -0500
On 24 Oct 2008, at 1:14 PM, Martin Redington wrote:
I created a static lib target, and added it as a dependency to my main
app target.
When I build I get the warning:
CodeSign warning: code signing is not enabled for product type Mach-O
Static Library
I am ignorant of the details of iPhone development, but it seems to me
that if Xcode does not support signing static libraries (which does
make sense -- they're not end-user deliverables), the thing to do is
not to attempt to sign them.
Did you, possibly, set your code-signing build settings at the project
level? You could tell by seeing if those settings are in bold in the
Build list of the Project Info window, and regular-weight in the Build
list of the Target Info window. If the latter is regular-weight, those
settings are "inherited" from the project.
Open the Target Info window for your library target (double-clicking
it in the Targets list in Groups & Files is the most direct way). Find
the code-signing settings. Set them so that signing isn't done. The
labels on those settings will become bold, showing that the settings
you made are for this target only.
I'm curious to know why you haven't upgraded to 3.1.1. It fixes bugs.
— 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