A few workflows concerning Carthage and nested framework
:warning: PRE-REQUISITES: :warning:️ In your github repo you need to include .xcodeproj file with framework settings all setup. The settings should also include:
$(SRCROOT)/Carthage/Build(Carthage generates aliases in this folder) aka magic portals to other frameworks.
.gitignorethat excludes .framework files and other binaries (We should never have bins in repos)
github "eonist/A" "master":point_left: Informs carthage to build this before anything else
github "eonist/B" "master"
carthage updateNow everything will download and be built in the right order. Children first :key:
carthage update --no-build(this downloads all repos but skips building)
If project owners include .framework files in their releases. (Some do, some don’t) then using
carthage update --no-build
And the binaries will be placed in
Don’t do it, Google it if your not familiar with why you shouldn’t use submodules for nesting dependencies
Which workflow is better? The future is automated so go with option 1. Also you need something that can work in a CI environment. The first workflow has a bit more bloat attached and carthage could have avoided this by allowing order take priority when building. (Feature request!!!) :point_right: The optional workflows are written down in order to justify the extra contextual files one has to place in sub dependencies. :point_left: