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 you
> 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
scott_r...@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice
On Apr 10, 2010, at 3:51 PM, Fritz Anderson wrote:
> Did you change the action type to Cocoa after starting with AppleScript or
> shell script?
No
> Have you examined the contents of the action bundle in the problem case?
> Clean the target first, then build. Control-click Products > yourBund
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 mak
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
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 'Execut
