Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

linking to libs that use a different build location is working now?

At this point it is generally nice to have a shared build
location so that all your build products end up in the same
place.

In fact this is not just nice but essential - Xcode will get the
dependencies wrong if the various products don't build in the same
place.
Originally I was of this opinion, but since Xcode 2.3 I've been linking to library subprojects that use different build locations without problems.

There was a "improved support for suprojects using diffferent build locations" (or similar) release note which I took to mean this issue was fixed.

Anyone have anecdotes to the contrary/caveats etc or is this actually fixed now?

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden
References: 
 >Re: [ANN] Xcode + Leopard at WWDC this year (From: "Andy O'Meara" <email@hidden>)
 >Re: [ANN] Xcode + Leopard at WWDC this year (From: Laurence Harris <email@hidden>)
 >Re: [ANN] Xcode + Leopard at WWDC this year (From: Adrian Hoe 贺文耀 <email@hidden>)
 >OT: How to file a radar WAS Re: [ANN] Xcode + Leopard at WWDC this year (From: Chris Forsythe <email@hidden>)
 >Re: OT: How to file a radar WAS Re: [ANN] Xcode + Leopard at WWDC this year (From: Adrian Hoe 贺文耀 <email@hidden>)
 >Re: Radar issues (Re: How to file a radar) (From: "James Larcombe" <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.