Re: Debug/Release Library Matching
Re: Debug/Release Library Matching
- Subject: Re: Debug/Release Library Matching
- From: Chris Bergmann <email@hidden>
- Date: Mon, 5 Sep 2005 20:13:43 +1000
A word of warning in advance; I've found xcode to be very unreliable about this kind of thing. I've customised the build settings (difficult, but possible) to allow customised input/output paths per build style, similar to the normal use in MSVC. It mostly works but every now and again xcode gets horribly confused and I need to clean build the entire set of projects and sometimes manually delete temporaries. The symptom here is that everything builds okay, but the target executable is not produced (or, is not produced in the correct location) and so run/debug fails. YMMV.
It's entirely possibly something i've set up incorrectly, but there's no meaningful errors or documentation on this area of the program, so I've no idea what that might be :)
chris
On 04/09/2005, at 17:22 , Chris Espinosa wrote: On Sep 3, 2005, at 11:23 PM, David Spells wrote:
What about Frameworks and bundles?
I want code to copy in the debug Framework into my debug application, and the release Framework into my release application. Don't I have to use the copy files build phase to do this? The copy files build phase seems to be target dependent.
Yes, and you can use the $(BUILT_PRODUCTS_DIR) build setting to find the built products of other projects on a per-configuration basis. So your Debug configuration's Copy Files phase would copy the Debug version of the private framework, and the Release configuration would copy the Release version,
Chris
|
_______________________________________________
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