Here are some possibilities:— Wrong target membership for files that are in the project.— Incomplete or inconsistent designation of frameworks header files as private or public vs. project.— Improperly updated include or frameworks header paths in the build settings.— Improper file referencing styles for the frameworks (e.g. absolute where you need build-products-relative, etc)— Inconsistent or unexpected use of modules (off/on) for frameworks.— Incorrect or conflicting module names for frameworks (it got parameterized a couple of Xcodes ago).— Errors/inconsistencies in schemes.I'd suggest you try working through your targets individually, starting with the ones that have no other project framework dependencies, then moving on to the ones that depend on them. Check (or create) the scheme for each target, set it as the current scheme and make sure you can build each framework in turn.Worst case, you can start looking at the compiler invocation lines for steps in the
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: