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:08:20 -0500
On 10 Apr 2010, at 2:01 PM, Steve Cronin wrote:
> I have an Automator action that is giving me a confusing result.
>
> If I include an 'Executable File' key in the info.plist
> - debug compile - with no executable this key is pointless
> - release compile - no warning
>
> If I remove the 'Executable File' key from the info.plist
> - debug compile - no warnings
> - release compile - bundle has executable but no CFBundleExecutable key
>
> Damned if I do and damned if I don't….
> Should I just include the key and ignore the debug compile warnings?
> Is there a compiler flag that I should be more informed about?
You don't say what kind of Automator action you are building — script, AppleScript, or Cocoa? And what do you mean by "compile warnings?" The compiler doesn't know or care about the contents of Info.plist. The build system might. But as far as I can tell by your message, the build system didn't complain at all — you only state your opinion that the key is "pointless."
And why does your action have "no executable" on debug compiles (or with the CFBundleExecutable key present), and "has executable" on release compiles (or with the key absent)? The presence of the key has no effect on whether a binary is built. The build configuration has no effect on whether a binary is built (modulo some really perverse build settings).
Xcode 3.1.3 (you'd do well to tell us what version of Xcode and what SDK you're using, and how you created your project):
I created a kill-me scripted action in Xcode, from the template. Info.plist had no CFBundleExecutable, which makes sense. There is a file that executes — the script — but that's now what I understand the key to mean.
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.
The templates as they are instantiated do the right thing, and in both cases, the actions build without complaint (though there was a category key the Info.plist processor wanted filled-in).
Would you please clarify your problem?
— 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