Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Target dependencies vs. configurations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Target dependencies vs. configurations

Subject: Target dependencies vs. configurations
From: James Walker <email@hidden>
Date: Fri, 09 Feb 2007 16:16:18 -0800

Let's say I have a target that produces a private framework, and another target that produces an app that uses that framework. (Maybe these two targets are in different projects, I don't know if that matters.) Now, as far as I know, there is no reasonable way to make the app's debug configuration link against the debug configuration of the framework, and the app's release configuration link against the release configuration of the framework, so let's say both configurations of the app link against the release version of the framework. Am I correct that if I make the app target depend on the framework target, then building the debug configuration of the app will build the debug configuration of the framework, which does no good? -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> _______________________________________________ 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 Follow-Ups: Re: Target dependencies vs. configurations From: Chris Espinosa <email@hidden> Re: Target dependencies vs. configurations From: James Bucanek <email@hidden> Prev by Date: Re: Using fstream Next by Date: Version.plist preprocessing Previous by thread: [Q] Jar and Xcode Next by thread: Re: Target dependencies vs. configurations Index(es): Date Thread