Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
Re: automated builds of Automator actions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: automated builds of Automator actions




On Nov 28, 2005, at 7:52 AM, Jim Matthews wrote:

We've run into a couple of issues with doing automated builds of Automator actions. We want our builds to depend on the current state of the source control repository, as opposed to the state of the build machine.

1) The AppleScript Automator action template in Xcode stores scripts in .applescript text files, and compiles them at build time with osacompile. We want to make sure that osacompile uses the correct dictionary -- the dictionary for the version of the app we are in the process of building. We'd rather not have to have a copy of the app installed on the build machine, and even then having osascript compile against whatever copy of the app that it finds on the build machine would not give us the sort of predictable results we're looking for. However, there does not appear to be a way to pass a .sdef or aete resource to osacompile -- am I missing something?

Nope. This is (IMO) a big issue with Automator at the moment. I've logged this in Radar and you should too :)


-tim

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Automator-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >automated builds of Automator actions (From: Jim Matthews <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2011 Apple Inc. All rights reserved.