Re: Automator Actions and CFBundleExecutable key
Re: Automator Actions and CFBundleExecutable key
- Subject: Re: Automator Actions and CFBundleExecutable key
- From: Steve Cronin <email@hidden>
- Date: Sat, 10 Apr 2010 15:19:10 -0500
On Apr 10, 2010, at 3:08 PM, Fritz Anderson wrote:
> You don't say what kind of Automator action you are building — script, AppleScript, or Cocoa?
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."
my bad 'compiler warnings'
PhaseScriptExecution "Run Script" "build/XYZ.build/Debug/New Foo From Files.build/Script-AA5E153E10B0AFCF0082C21B.sh"
cd /Volumes/DaBook/Projects/myProject/XYZ/Code
..
/bin/sh -c "\"/Volumes/DaBook/Projects/myProject/XYZ/Code/build/XYZ.build/Debug/New Foo From Files.build/Script-AA5E153E10B0AFCF0082C21B.sh\""
warning: CFBundleExecutable key is pointless with no executable.
Run Script: /usr/bin/amlint "${BUILT_PRODUCTS_DIR}/${FULL_PRODUCT_NAME}"
>
> 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).
It has the key - I merely cited the outcomes based on two different setups that I had constructed trying to understand what is going on...
I have the key and remain puzzled by the 'pointless' warning that is tossed off as show immediately above
> 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):
XC 3.2.1 SDK 10.6
>
> 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?
>
> Would you please clarify your problem?
Trying
_______________________________________________
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