The submodules are causing an issue when including AlamofireObjectMapper via Carthage (not using the --use-submodules option). The issue seems to be that the submodules are being checked out by Carthage when it is cloning/fetching AlamofireObjectMapper. Because of this, the framework is being build against the commit/versions of ObjectMapper and Alamofire that the submodules points to, instead of the versions that have been resolved by Carthage. I think this is what is causing the issue with https://github.com/tristanhimmelman/AlamofireObjectMapper/issues/147.
If we remove the submodules, this would mean that when someone clones this project, they will need to either use Carthage to checkout the dependencies, or clone them manually themselves, to be able to build the project.
I'm not sure if this is the best fix, but it does get Carthage working again
The submodules are causing an issue when including
AlamofireObjectMapperviaCarthage(not using the--use-submodulesoption). The issue seems to be that the submodules are being checked out byCarthagewhen it is cloning/fetchingAlamofireObjectMapper. Because of this, the framework is being build against the commit/versions ofObjectMapperandAlamofirethat the submodules points to, instead of the versions that have been resolved byCarthage. I think this is what is causing the issue with https://github.com/tristanhimmelman/AlamofireObjectMapper/issues/147.If we remove the submodules, this would mean that when someone clones this project, they will need to either use
Carthageto checkout the dependencies, or clone them manually themselves, to be able to build the project.I'm not sure if this is the best fix, but it does get
Carthageworking again