building my debug app against my debug framework, and my release app against my release framework
building my debug app against my debug framework, and my release app against my release framework
- Subject: building my debug app against my debug framework, and my release app against my release framework
- From: "John C. Daub" <email@hidden>
- Date: Mon, 19 Dec 2005 16:32:59 -0600
- Thread-topic: building my debug app against my debug framework, and my release app against my release framework
Hello.
I have a setup where I build a framework, then another couple of frameworks
link against that framework, then I've got an app that links against all
those frameworks, and some plugins the app loads which are also built
against those frameworks.
I'm finally able to upgrade a particular project from Xcode 1.5 to Xcode
2.2, and with the change from build styles to configurations, things broke
because of how the built binaries are now output to individual configuration
subfolders within the build directory (projects depending upon the previous
framework projects can't find the framework headers, can't find the
framework for linking, etc.). I know this is not a new issue, as scanning
the mailing list archives show others have encountered this problem as well.
Unfortunately, I've not been able to find an answer to this problem in the
mailing list archives. Or at least, what messages I found from Xcode 2.0 and
2.1 postings was that there isn't a good solution to this problem.
I'm wondering if this situation has been remedied in Xcode 2.2?
I noticed a setting "Per-configuration Build Products Path", that defaults
to $(BUILD_DIR)/$(CONFIGURATION). Would I be able to adequately resolve this
problem by setting this in the framework projects to just $(BUILD_DIR)?
Granted each time I build it'll blow away the previous version and so it'll
have to rebuild each time I deal with a different configuration. But I'm
wondering if this is an acceptable solution to this problem... if I do what
I suggest above, if I'm going to have problems, etc..
If there's no Xcode 2.2 solution and the above path setting tweak doesn't
solve the problem... what is the solution to this issue?
Thanx.
--
John C. Daub }:-)>=
<mailto:email@hidden> <http://www.hsoi.com/>
Peace on the Earth, goodwill to men.
_______________________________________________
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