opensubscriber
   Find in this group all groups
 
Unknown more information…

a : automator-dev@lists.apple.com 28 November 2005 • 11:52PM -0500

automated builds of Automator actions
by Jim Matthews

REPLY TO AUTHOR
 
REPLY TO GROUP




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?

2) amlint tries to make sure that custom data types are defined by a
.definition bundle in /System/Library/Automator, ~/Library/Automator,
etc.  But the build machine won't have the freshly-built .definition
bundle installed (in general we try to install as little software on
the build machine as possible).  Is there a way to tell amlint to
look in a build products folder (short of customizing the amlint
script itself)?

Thanks,
--
Jim Matthews
Fetch Softworks
http://fetchsoftworks.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Automator-dev mailing list      (Automator-dev@list...)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/automator-dev/subscriber%40opensubscriber.com

This email sent to subscriber@open...

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.