Xcode dependencies across different build directories?
Xcode dependencies across different build directories?
- Subject: Xcode dependencies across different build directories?
- From: Starkos <email@hidden>
- Date: Tue, 22 Sep 2009 08:59:44 -0400
I am trying to set up an Xcode project which contains multiple
executables and static libraries. I have created multiple targets and
set up the linking and dependencies, and initially everything works
great. The catch...
This is an existing project which already has Visual Studio and
Makefile builds. Those builds put the libraries in a lib/Debug
directory and the executables in bin/Debug. So in Xcode I changed the
Build Products Path to "lib" and "bin" respectively. This puts the
compiled targets in the right place (so we can use one set of
documentation for all of the platforms), but completely breaks both
the linking (Library not found) and the dependencies.
I can fix the linking by adding $(SRCROOT)/lib/Debug to the Library
Search Paths for each executable (but it feels like Xcode should be
able to figure this out on its own, which makes me think I'm doing
something wrong).
But — I can't figure out how to get the dependencies working again. If
I change a library source file, the library will rebuild but not the
dependent executables. If I force a build of the executable Xcode
returns success without doing anything; it thinks the target is up to
date. If I clean the target and then rebuild it works.
So, any ideas here? Is Xcode being fundamentally stupid in this
regard, or is it me (I'm leaning toward the latter)?
(FYI I also asked this question on StackOverflow:
http://stackoverflow.com/questions/1456806/xcode-dependencies-across-different-build-directories)
Many thanks for any help with this,
-st.
_______________________________________________
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