Re: Automator Actions and CFBundleExecutable key
Re: Automator Actions and CFBundleExecutable key
- Subject: Re: Automator Actions and CFBundleExecutable key
- From: Fritz Anderson <email@hidden>
- Date: Sat, 10 Apr 2010 15:51:22 -0500
On 10 Apr 2010, at 3:19 PM, Steve Cronin wrote:
> XC 3.2.1 SDK 10.6
My mistake; I said 3.1.3 (which is the iPhone OS). I meant 3.2.2. 10.6 SDK.
>> I created a kill-me Cocoa action in Xcode, from the template. Info.plist ha a CFBundleExecutable key, set to ${EXECUTABLE_NAME}. Again, this makes sense, because the plug-in has a binary executable.
>>
> So what happens if you compile for debug?
Build succeeded. No warnings.
Did you change the action type to Cocoa after starting with AppleScript or shell script? I'm betting that different run-script-phase scripts come from the template depending on the type, and changing the type will do the Wrong Thing.
Have you examined the contents of the action bundle in the problem case? Clean the target first, then build. Control-click Products > yourBundle in the Groups & Files list, and Show in Finder. Control-click on the icon and Show Package Contents. (You know all this, but I'm appallingly thorough.)
Is the executable there? Is the processed Info.plist as you expect? (Examine it with a text editor or Open As > Source in Xcode; the graphical plist editor can be deceiving.)
— F
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden