Setting up Cross Project Dependencies
Setting up Cross Project Dependencies
- Subject: Setting up Cross Project Dependencies
- From: Mike Jackson <email@hidden>
- Date: Fri, 8 Jul 2005 12:22:08 -0400
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.
I then thought about adding both the debug and the release
versions of the dylibs that were created under project number 1 into
project number 2, but soon found out that there isn't a way to assign
a dependent lib to a build configuration, just a target. So that
leads me to believe that I need to have 2 actual targets in project
number 2, one for debug and one for release. I would be willing to go
down that route except for the fact that the last project already has
about 20 targets. This would double that to 40 which is getting a bit
unreasonable to me.
Is there something I am just not "getting" about Xcode. I would
really like to just understand how to do things the "right" way.
Thanks for any and all help/pointers/info.
---
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