Re: Derived source compilation
Re: Derived source compilation
- Subject: Re: Derived source compilation
- From: Dair Grant <email@hidden>
- Date: Mon, 25 Jun 2007 23:49:38 +0100
Jonas Maebe wrote:
There's also an extra issue with this: Xcode does not guarantee
when a Script Phase will be run with regard to the other
phases inside a target, apart from explicitly mentioned
dependencies in the input/ output file settings.
Yes, this is really the feature I need - I dragged the script up
above Build Sources, but it's still executed after dependencies
are checked.
I can generate the source as required, compile it, and use a
-filelist to insert those .o's into the link. However I can't
force a re-link when the script determined something was dirty,
since Xcode has already done its dependency checking before I run.
Processing derived sources which are implicitly generated by a Run
Script are, I think, inherently unsupportable in this setup (except
if the Run Script phase resides inside its own subtarget, since
subtargets are guaranteed to execute before the rest of the "parent"
target executes).
That would be another option, however there's no clean way for
that target to know which target in the project invoked it -
really i'd like to handle it all in one script in one target.
I think the closest I can get is a non-zero exit value when my
script determines it had to do something. That will stop the
build, forcing you to hit Build again (which is ugly, but safer
than having the generated source be out of step with the executable).
Ideally a Run Script placed above Build Sources would execute
before any part of building, including dependency checking.
-dair
___________________________________________________
email@hidden http://www.deathvalleycycle.com/
_______________________________________________
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