Edit Question - KnowledgeHub

Title Body

Overview I'm using static libraries and Xcode 4 workspaces to effect modularity in iOS development, an increasingly common technique. For example, I might have a workspace which contains an App project, and a Library project, like so 1 : You would then have a scheme to build these that looked something like this: What I would like to do is have the "App build" control the "Library build" it initiates, in at least a couple of ways: Map App configurations (e.g. Debug, AdHoc) to arbitrary Library configurations Passing through some subset of -D defines, and/or specifying these for the library build. I'll deal with each of these in their own section, but it's worth making a few clarifications. Clarifications I'm using App/Library here as an easy proxy for any Superproject/Subproject relationship you may have. From what I've seen, Xcode 3 style embedded subprojects don't seem to work any differently in Xcode 4 than workspace "peers". I'd love to be wrong about this. I know I could do almost anything with a "Run Build Script" build phase, and xcodebuild. But I'm trying to work within the system here, where the dependencies are specified in the scheme, and otherwise somewhat loosely coupled. The Library exists to be used in more than just this project, and so you cannot arbitrarily load it up with junk specific to this App's build, or reference anything particular to the App or Workspace. For the general case, this rules out including static .xcconfig from the App project as a way to convey build information from the App to the Library. Building the Library outside the workspace sacrifices too much, no

Tags (comma-separated) Cancel