Re: passing info from main project to subproject
Re: passing info from main project to subproject
- Subject: Re: passing info from main project to subproject
- From: "Peter Lau" <email@hidden>
- Date: Wed, 23 May 2007 23:33:42 -0400
It seems like in your example that MORE_CONTENTS is not being defined
consistently between your library and application projects. Are both
projects referencing the same .pch file?
No they don't... my thought is not to use any file but simply passing
a #define value from the main project to the cross-project
references.
FWIW, since I use a large number of common sources amongst several
projects/targets, I've created one project to build a static library
containing the shared bits, then the other targets just link against
the static library. This hugely speeds up my overall build process.
Build #defines that turn various features on/off are contained in a
header file included in a .pch file that is pre-compiled once and
then used by all targets. This works just fine for me and everything
stays in synch.
I have a similar set up, the one static library will compile into a
couple of application projects. Now, I want to expand my static
library project but I don't want the new code gets compile into those
existing applications when I compile them.
So, I have a #define in the library project with the default value to
zero... when I compile the application projects, the #define will
excluded the new code.
To test the new code, I have a third application project just for that
purpose... I was hoping from this third application project, I can set
the #define value to one and then pass the value onto the static
library project, without changing any config or target settings.
But looks like Xcode does not let me do that within the Xcode setup...
pete
_______________________________________________
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