Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Preprocess Info.plist for Single-File Tool

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Preprocess Info.plist for Single-File Tool

Subject: Preprocess Info.plist for Single-File Tool
From: Jerry Krinock <email@hidden>
Date: Fri, 15 May 2009 20:00:16 -0700

I've added Info.plist files to my single-file tool products as explained in Apple's Code Signing Guide [1]. It seems that, exactly as has been reported by K. Moskowski [2], Info.plist preprocessing does not work.

Apparently, this technique embeds the Info.plist into the product executable. But when I examine the product with otool -sv __TEXT __info_plist, I see that the ${YADDA.YADDA} symbols are still in there even after I delete the product, touch the Info.plist source, clean, rebuild, etc.

I hope maybe someone can tell me the trick I'm missing, because I have had trouble in the past getting Xcode to "notice" Info.plist changes. Otherwise, if no one replies with a reason why this should not work as expected I'll file a bug next week. This is Xcode 3.1.2.

Thanks,

Jerry Krinock

[1] http://developer.apple.com/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html#/ /apple_ref/doc/uid/TP40005929-CH4-DontLinkElementID_6

[2] http://www.cocoabuilder.com/archive/message/xcode/2009/3/4/27550
_______________________________________________
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



Prev by Date:
Re: Passing PREPROCESSOR_MACROS as input to XCode build

Next by Date:
Re: Release Version Not Appearing

Previous by thread:
Re: Passing PREPROCESSOR_MACROS as input to XCode build

Next by thread:
Re: Preprocess Info.plist for Single-File Tool

Index(es):

Date
Thread