Re: cp from Xcode Shell script target
Re: cp from Xcode Shell script target
- Subject: Re: cp from Xcode Shell script target
- From: "Paul Sanders" <email@hidden>
- Date: Fri, 5 Mar 2010 21:25:12 -0000
That is very interesting (and a little unnerving). What a
horrible piece of design (or maybe implementation). Thank you
gentlemen.
Paul Sanders,
----- Original Message -----
From: "JT Burgess" <email@hidden>
To: "Greg Guerin" <email@hidden>
Cc: "list Xcode-users" <email@hidden>
Sent: Friday, March 05, 2010 8:18 PM
Subject: Re: cp from Xcode Shell script target
That seemed to fix it! Thanks!
For posterity, I was creating the Process.app directory first,
then
slowly adding things to it, so your explanation is probably
correct.
On Fri, Mar 5, 2010 at 3:02 PM, Greg Guerin <email@hidden>
wrote:
> It could be that Finder or LaunchServices reads the contents
> of the new app,
> in the middle of the process of building it. Your cp comes
> later and
> changes things, and LS isn't told again to read the contents,
> so its
> database is stale.
>
> One way I've remedied this is to touch the top-level dir (i.e.
> the .app)
> after making changes inside the .app. This causes Finder or LS
> to see a
> different mod-date on the top-level app, and trigger an LS
> update. The
> glitch comes because Finder won't look *inside* an app-bundle
> for newer
> mod-dates, so the fix essentially propagates the internal
> mod-date out to a
> place where Finder (or LS) will see it.
_______________________________________________
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