Xcode Project References
Xcode Project References
- Subject: Xcode Project References
- From: j o a r <email@hidden>
- Date: Wed, 9 Jun 2004 08:25:55 +0200
Preciously little is know about them it seems. As far as documentation
goes, this is what I've been able to dig up:
Xcode 1.0 release notes
=================================================================
Project References An Xcode project can refer to another project by
including the other project's project file in its Groups & Files tree
(adding it as any other file). A project which does this can then make
its targets depend on targets in the referenced project, and can
include the products of the referenced project's targets in its own
targets. This feature works best when all linked projects share a
central build directory.
=================================================================
Scott Tooker, on this mailing list
=================================================================
Currently, the buildstyle used in the master project is sent to all
other targets (including those referenced from other projects).
=================================================================
Where would I find more information? Any suggestions are appreciated!
Project References holds a lot of promise, especially for building
components that are shared between several projects (frameworks,
et.c.), but they seem to still suffer from either a couple of problems,
or perhaps only a lack of documentation.
What would be interesting to know is what is propagated from the main
project to the referenced projects. Scott Tooker suggests that the
values from the build style are sent, and that seems to be the case.
While this is good for such things as, oh I don't know - optimization
level, warning flags, et.c. - it doesn't quite work for prefix header
file and other obviously project specific settings. I guess that the
answer to that problem is to move these build settings to the targets,
instead of setting them in the build style? That is of course doable,
but it is often very convenient to set "shared" build settings in the
build style instead of having to propagate them to all (in our case
over 100) targets in the main project. I have previously requested
"target groups" that could be used to set shared build settings - I
hope that is being considered.
Will build settings passed from the main project to a referenced
project simply replace all build settings in the referenced project, or
are they somehow merged?
It seems that the build directory location is not propagated from the
main project to the referenced projects? It's also suggested in the
release notes quoted above, even though it's a bit unclear exactly why
the suggestion is made. This is IMO very unfortunate, as it makes it
almost impossible (at least much more cumbersome and error prone) to
use project references in large projects where you need to work on
multiple branches of the project simultaneously (As you can't set a
custom build folder in the main project only, or pass it to xcodebuild,
and expect it to be used also for referenced projects. You would need
to remember to set it for all referenced projects - which also implies
that you need to have an in depth knowledge of the project architecture
in order to not screw up.).
Finally, I hope that the absence of Xcode development team
representatives on this list recently indicates that you're all hard at
work with bringing us a new version of Xcode for WWDC? ;)
Regards,
j o a r
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.