-1

I have an Xcode 4 workspace which contains 2 projects:

  • Demo app that uses a static library
  • Project with a static library target

I have configured everything correctly according to this Apple document and everything builds, links and runs fine.

In the scheme settings for the demo app I have the static library target above the demo project in the build->target panel, so I believe the dependancies are all okay.

If I make a change to the static library project (but don't touch the demo project - which is the current scheme) and then build & run the app, I can see that the static library project gets built and Libtool creates the new .a file. The problem is the demo project isn't touched, and therefore the changes that I made to the static library aren't used. The only way to get around it is to do a complete clean and re-build for the whole workspace, which is obviously not ideal.

Does anyone know how I can get the demo app to include the updated static library without forcing a clean with every change?

Michael Waterfall
  • 20,497
  • 27
  • 111
  • 168
  • Maybe the following question will help you: [How should I manage dependencies across projects in an Xcode workspace?](http://stackoverflow.com/questions/5483909/how-should-i-manage-dependencies-across-projects-in-an-xcode-workspace) – iHunter Jan 01 '12 at 18:57
  • Thanks that did help. I'm sure the whole thing isn't quite right though, dependencies aren't being properly tracked with both projects as siblings in the workspace. Very strange! – Michael Waterfall Jan 09 '12 at 16:38

0 Answers0