Re: Inter-project dependencies
Re: Inter-project dependencies
- Subject: Re: Inter-project dependencies
- From: Daniel Jalkut <email@hidden>
- Date: Wed, 21 Dec 2005 19:51:01 -0500
James - with the caveat that I've not reviewed your email too
carefully, let me throw out a few points:
1. Inter-project dependencies seem to require that you set the "Build
Locations" settings for all projects involved to the same locaiton.
2. Simply adding the subsidiary project and checking its product as
part of a "super project" will not cause the desired dependency
chain. You have to click the "super project" target you want to
"depend on" the subsidiary, open its Inspector window, click the
"General" tab, and then in the lower left corner click the + icon to
add a dependency. At this point the built product you select shows up
inside the target, as a sort of "pseudo-build phase."
3. Even when everything works - sometimes it doesn't. I've observed
from time to time that, especially while getting the kinks ironed
out, you have to open a subsidiary product and manually build it.
Maybe these oblique blows toward solving your problem will be of some
help :)
Daniel
On Dec 21, 2005, at 4:25 PM, James Milne wrote:
I have two three projects in my application:
Base.xcodeproj
Framework.xcodeproj
App.xcodeproj
Base.xcodeproj and Framework.xcodeproj produce static libraries.
App.xcodeproj in this case creates a command-line application.
I wish to define dependencies in App.xcodeproj so that building
App.xcodeproj causes Base.xcodeproj and Framework.xcodeproj to be
rebuilt if they are out of date.
I figured that it would be possible to do this if I simply dragged
the project files from Base and Framework into App.xcodeproj. When
I do this, Xcode acknowledges this action and shows the build
products of these projects in the App.xcodeproj project browser. I
check the checkbox to target the build products from these projects
for inclusion in App.xcodeproj.
The problem occurs when I build App.xcodeproj. The build system
doesn't seem to be able to locate the static library files for Base
and Framework. I get an error of the following form:
Bundlizing /Development/VisualScience/TNT/Version1/ViSOSExamples/
Code/BasicServices/build/BasicServices.build/Debug/
BasicServices.build/Objects-normal/ppc/libVisosFramework.ab build/
Debug/libVisosFramework.a
cd /Development/VisualScience/TNT/Version1/ViSOSExamples/Code/
BasicServices
/usr/bin/gcc-4.0 -bundle -arch ppc build/Debug/
libVisosFramework.a -Wl,-all_load -mmacosx-version-min=10.4 -Wl,-
twolevel_namespace -Wl,-twolevel_namespace_hints -Wl,-undefined -
Wl,dynamic_lookup -Wl,-multiply_defined -Wl,suppress -isysroot /
Developer/SDKs/MacOSX10.4u.sdk -o /Development/VisualScience/TNT/
Version1/ViSOSExamples/Code/BasicServices/build/BasicServices.build/
Debug/BasicServices.build/Objects-normal/ppc/libVisosFramework.ab
powerpc-apple-darwin8-gcc-4.0.1: build/Debug/libVisosFramework.a:
No such file or directory
I would have though that if Xcode could analyse the xcodeproj files
I dragged into App.xcodeproj, it would have been able to sort out
the library include paths so that the build results from Base and
Framework could be linked into the application generated by
App.xcodeproj.
Am I doing something wrong here? The documentation that comes with
Xcode is a bit too 'introductory', and doesn't seem to cover
setting up this sort of relationship between .xcodeproj files.
--
Kind regards,
James Milne
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
sweater.com
This email sent to email@hidden
_______________________________________________
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