therealmyluckyday
commented
7 years ago I have been trying to find a solution to this, so far the only thing that works is use carthage as a dependency manager in my project (which manages to build CardIO.framework) and then archive CardIO.framework in a zip and use it as the source of a private pod (CustomCardIO) that I then specify as a dependency of my project in its podspec. It works correctly but I have to maintain versioning manually whenever I want to update CardIO.
Right now I am looking into forking this project and configuring my own podspec but for the moment I am stuck because pod spec lint keeps failing (it can't create CardIO.framework). I don't know why CocoaPods fails when Carthage succeeds but I don't know enough about CocoaPods and build configuration to make it work
General information
Issue description
When trying to add CardIO as a dependency inside my own pod, I get this issue when running pod update on the main project:
target has transitive dependencies that include static binaries: (.../ProjectName/Pods/CardIO/CardIO/libCardIO.a, ../ProjectName/Pods/CardIO/CardIO/libopencv_core.a, and ../ProjectName/Pods/CardIO/CardIO/libopencv_imgproc.a)
Is there any known way to workaround this? The only solutions I found are to ship this as a dynamic.