Re: Setting up Cross Project Dependencies
Re: Setting up Cross Project Dependencies
- Subject: Re: Setting up Cross Project Dependencies
- From: Mike Jackson <email@hidden>
- Date: Fri, 8 Jul 2005 13:09:53 -0400
On Jul 8, 2005, at 12:38 PM, Mark Bessey wrote:
On Jul 8, 2005, at 9:22 AM, Mike Jackson wrote:
I am attempting to port some Linux/Win32 Libraries. There are
about 6 total. They all are dependent on one of the Projects. So I
built this first and that is fine. I have a debug and a release
build folders which kinda works out good in the long run. My
question is how do I leverage those two different builds for the
Second Project that depends on the first Project? I look at the
docs for cross project dependencies and while this makes sense,
every time I build the Second project, the first is rebuilt and re-
linked.
Hmm. That shouldn't happen unless you've got some sort of circular
dependency. Does building the "Second" project affect any of the
sources in the first project?
As for the other half of your question, it sounds like you're
trying to add the built libraries from the filesystem to your
second project's link phase. That's not the way to do this. If you
open the "Second" project, and click the disclosure triangle next
to the referenced project, you'll see a list of the products
produced by that project. You want to drag those to the link phase
of the project. That way, Xcode will take care of matching up the
debug & release versions to the appropriate build.
-Mark
Thanks that worked. Now when I clean the "Second" Project only the
products for that "Second" project get cleaned and then built. This
is generally what I am after.
The next question I have would be what is the best way to go about
rebuilding each project. Should I create an aggregate target in the
"Second" project that has the "First" project as a direct dependency?
Wouldn't "Building" that aggregate target then make sure the other
projects are built and up to date?
I tried my own advice and adding the aggregate Target seemed to work,
but it doesn't seem to be picking up the fact that for debug builds
we put and "_d" on the name of the lib (libSecond_d.dylib and do NOT
put it on there for the release builds (libSecond.dylib). Using the
"Debug" build configuration worked as expected but using the
"Release" build configuration tried to look for libSecond_d.dylib
instead of libSecond.dylib. When using an Aggregate Target, does
Xcode use the current build configuration when checking/rebuilding
dependent projects?
Thanks
---
Mike Jackson
mike _at_ bluequartz dot net
_______________________________________________
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