Dependencies can't find their nested dependencies about carthage HOT 1 CLOSED

This will be a fairly complicated undertaking. We need to do each of the following things, mostly in order:

1. Read the application project's Cartfile.lock.
2. Build dependencies that have no dependencies themselves.
3. Build other dependencies, giving them access to the previously built dependencies somehow. (This is where I started talking about symlinks above.)
4. Copy the built product from each dependency into the application project's Carthage.build.

The key points here are that each dependency exists as a sibling folder of all other dependencies, nested under the application project's folder.

Consequently, we need to do some M A G I C so that these siblings can use built products from each other—maybe that means symlinks, or maybe it means being smarter about how we build in the first place. Then, we need to collect all the built products and put them into the root folder, for use by the application project.

Any solution that we implement also needs to ensure that a framework project works just as well with carthage build --no-skip-current (i.e., when built as a standalone project) as it does when built as a dependency of another project.

from carthage.