In relation to the partial add of Carthage in PR #12
Carthage support is partial since Carthage tries to use the XCode project to build the frameworks when included as a dependency in another project.
The current XCode project only builds after a executing pod install
Current workaround is to
carthage update --no-build
pushd Carthage/Checkouts/sReto/Source/
pod install
popd
carthage build
In order to fix this issue, the example project would need to be fixed to build successfully without executing any additional commands.
This could be done in 2 ways,
- Include the sub-dependency projects directly in this repo after a
pod setup by modifying the .gitignore rules to include the checked out source.
- Change the project to use Carthage instead of cocoapods, since Carthage will find the sub-dependencies listed in this projects
Cartfile, checkout and build and create proper symlinks to the shared checkout after resolving version mappings.
I suggest solution 2, which would still maintain Cocoapods support side by side to Carthage support.
In relation to the partial add of Carthage in PR #12
Carthage support is partial since Carthage tries to use the XCode project to build the frameworks when included as a dependency in another project.
The current XCode project only builds after a executing
pod installCurrent workaround is to
In order to fix this issue, the example project would need to be fixed to build successfully without executing any additional commands.
This could be done in 2 ways,
pod setupby modifying the.gitignorerules to include the checked out source.Cartfile, checkout and build and create proper symlinks to the shared checkout after resolving version mappings.I suggest solution 2, which would still maintain Cocoapods support side by side to Carthage support.