Re: Setting up Cross Project Dependencies
Re: Setting up Cross Project Dependencies
- Subject: Re: Setting up Cross Project Dependencies
- From: Scott Tooker <email@hidden>
- Date: Fri, 8 Jul 2005 14:17:52 -0700
Sounds like. PLease file a bug, and provide a skeleton project to
demonstrate it.
Scott
On Jul 8, 2005, at 10:16 AM, Mike Jackson wrote:
On Jul 8, 2005, at 1:09 PM, Mike Jackson wrote:
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?
Hitting the "Build" button a 2nd time for the Aggregate target in
the "Second" project now links correctly. So if I switch to the
"Release" build configuration, the click build for the aggregate
target Xcode tries to link against the debug library in the
"Release" folder. Which it can not find because it is named
slightly differently for the debug versus the release build
configurations. If I then just click the "Build" button a second
time the project is linked correctly. Is this a bug by any chance?
---
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
_______________________________________________
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