• 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
Re: Automator Action doesn't see updated sdef
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Automator Action doesn't see updated sdef


  • Subject: Re: Automator Action doesn't see updated sdef
  • From: Chris Espinosa <email@hidden>
  • Date: Tue, 26 Dec 2006 16:18:50 -0800


On Dec 26, 2006, at 11:50 AM, Bill Cheeseman wrote:

on 2006-12-25 12:59 PM, Jerry Krinock at email@hidden wrote:

By doing a ps in Terminal, I found out that
Automator had decided that it liked an old version of my app that it had
dredged out of an archive folder, and was running this instead of the latest
version that I had installed in /Applications.

So, I finally got it to work by launching the new version of the app before
running the Automator action in Xcode.

Another voodoo incantation to add to the toolbox!

This has been standard practice since System 7 days.  Launch Services isn't noticeably better than the Desktop Database in this respect.

A trick I've learned to apply in several different contexts is this: Always
archive (zip) a previous version of any application you are developing
before starting work on the next version, and delete the original.

When developing new versions of my Cocoa apps, for example, I always archive
the source code and delete the old project files. Otherwise, I find that
Xcode is apt to index the wrong version's project files and open them when I
think I'm editing a file in the project for the next version.

A better way around this is to locate the project index files in the project directory, rather than in a shared cache.  

$ defaults write com.apple.Xcode XCCodeSenseIndexBasePath ./index

This ensures that if you open and build two projects that build to a common Intermediates directory and have the same project name, their indexes won't be coalesced, and the abovementioned problem (navigating from a file in one project and arriving at a file in the other) won't happen.  

You still have to be careful about the shared intermediates folder, in that if you build one project, then open and build the other, the up-to-date status may get fairly confused. 

Chris
 _______________________________________________
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

References: 
 >Re: Automator Action doesn't see updated sdef (From: Bill Cheeseman <email@hidden>)

  • Prev by Date: Re: Automator Action doesn't see updated sdef
  • Next by Date: Re: Setting a watchpoint in Xcode for a Java program
  • Previous by thread: Re: Automator Action doesn't see updated sdef
  • Next by thread: Re: Automator Action doesn't see updated sdef
  • Index(es):
    • Date
    • Thread