Re: Derived source compilation
Re: Derived source compilation
- Subject: Re: Derived source compilation
- From: Dair Grant <email@hidden>
- Date: Sun, 24 Jun 2007 00:13:50 +0100
Chris Espinosa wrote:
- Add the list of files generated to the Output Files list of the
Run Script phase.
...
- Drag all the derived sources into you Groups and Files tree, don't copy,
These are the steps I'd like to avoid - they both require
updating the project to reflect the current set of
files-that-produce-extra-output, which means extra work to keep
that in sync.
I can identify which files will generate additional source, and
can invoke make to ensure I'm not rebuilding them unnecessarily,
but I'd like to find a way to incorporate that source into the
project without having to mess with the project itself.
This technique will be used for projects using a library that
implements the code referenced by this dynamically-generated stuff.
I would like to pare it down to an "add a single Run Script
phase to the project" step, so that those projects have as
little extra configuration as possible (and don't need this
double-build process: they just add a .foo, or a
.h-with-a-special-macro, and any source produced by them gets
built too).
The closest I can think of would be to generate a
specially-named #include file, rewrite that to #include the
extra .cpp/.h files, and have a requirement that this header
gets pulled in once (e.g., by the source file that defines main).
I put an example at http://idisk.mac.com/cdespinosa/Public/ in
the DynamicSources folder. That shows the basic technique.
Thanks, I'll check that out.
-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