Re: Automator Actions and CFBundleExecutable key
Re: Automator Actions and CFBundleExecutable key
- Subject: Re: Automator Actions and CFBundleExecutable key
- From: Mark Munz <email@hidden>
- Date: Wed, 21 Apr 2010 21:35:15 -0700
I've run into this as well -- particularly with Automator Actions. I
decided to finally track down the issue.
The root cause appears to be that the RunScript Phase is being called
too early in the build process. So when amlint checks for an
executable, it hasn't been built yet.
If you look at your detailed log, you'll likely see that the RunScript
occurs right after resources are copies, but before the code is
compiled.
I put ${BUILT_PRODUCTS_DIR}/${FULL_PRODUCT_NAME} in the input files
list. Not sure if that is the proper way or not to force the Run
Script to wait for the actual product to be built, but it appears to
do the job.
Hope that helps.
Mark
On Sun, Apr 11, 2010 at 12:31 PM, Scott Ribe <email@hidden> wrote:
>> There are no other warnings tossed out during either compilation
>> Any thoughts?
>
> Compare the build transcripts for debug vs release for clues as to why debug
> is not producing an executable.
>
> --
> Scott Ribe
> email@hidden
> http://www.killerbytes.com/
> (303) 722-0567 voice
>
>
> _______________________________________________
>
> 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
>
--
Mark Munz
unmarked software
http://www.unmarked.com/
_______________________________________________
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