Re: Forcing a non-compile build phase?
Re: Forcing a non-compile build phase?
- Subject: Re: Forcing a non-compile build phase?
- From: Chris Espinosa <email@hidden>
- Date: Tue, 16 Oct 2007 21:54:38 -0700
On Oct 16, 2007, at 4:48 PM, Tim Conkling wrote: I have a Copy Bundle Resources build phase that copies a data folder into my app's Resources folder. I have a Folder Reference to this folder in the project, and I expected that any time the contents of the folder changed, the build phase would be run, but this isn't the case.
I can't figure out a way to get this phase to run without doing a clean build of my app (which takes forever to complete). Is it possible to force this build phase to run, or have it run without doing a full Clean first?
Currently we don't store a deep timestamp tree of everything in a folder reference in the dependency tree, so an arbitrary change in a folder reference won't, as you discovered, cause a rebuild. If you're going to be making a lot of changes to files not explicitly included in the project and want them to be copied into the executable, you might copy them with a Shell Script Build Phase that runs unilaterally, instead of a Copy Bundle Resources phase that only runs when a known member is changed.
Or you could add a "dummy" project member to that Copy Bundle Resources build phase and touch that dummy file to trigger copying of the folder reference.
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