• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Xcode & Automator
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode & Automator


  • Subject: Xcode & Automator
  • From: "Timothy J. Wood" <email@hidden>
  • Date: Tue, 13 Sep 2005 17:02:51 -0700


We have a bunch of actions bundled into one of our products and I'm updating how these get built. Ideally, I'd like to have the main application project contain a project reference to each of the action xcodeproj's. It can then build the .action bundles and have a Copy Files build phase that puts them in the Library/Automator sub-folder of the application.


The problem is osacompile. The target application must be running for osacompile to work, but I'm still in the middle of *building* the target application. This can be made to work, but is ugly when your AppleScript suite changes too quickly -- if the random copy of the app that osascript launches doesn't have the right dictionary, your actions might fail to build.

This, like much involving AppleScript, is horrifying. Any success stories out there? I can make this work, but I'd like it to be nice and clean so that our automated build system doesn't get into fits.

-tim


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Xcode & Automator
      • From: Mark Bessey <email@hidden>
  • Prev by Date: Debugging a bundle
  • Next by Date: Re: Debugging a bundle
  • Previous by thread: Re: Debugging a bundle
  • Next by thread: Re: Xcode & Automator
  • Index(es):
    • Date
    • Thread