I have a pod 'QSUtility',
and 'QSUtility' have vendored_libraries 'libleveldb.a' 'libmemenv.a' 'libsnappy.a'.
When I embed 'QSUtility' to my project 'Testtt' with cocoapods, and build it, the 'libleveldb.a' 'libmemenv.a' 'libsnappy.a' will link to the QSUtility.framework.
But!
When I embed 'QSUtility' to my project 'Testtt' with cocoapods-binary, and build it, the 'libleveldb.a' 'libmemenv.a' 'libsnappy.a' will link to the Testtt project target.
I think the '.a' files should link into QSUtility.framework
It seems some problem with vendored_libraries, could anyone please help me deal with it?
Thanks for your feedback!
If it's a bug:
What's your environment:
run pod env | egrep 'CocoaPods |Xcode|cocoapods-binary' then paste the result here
CocoaPods : 1.8.4
Xcode : 11.2 (11B52)
cocoapods-binary : 0.4.4
A demo project is helpful:
It will be very helpful if provides a demo project that reproduce the problem. A blank project with cocoapods-binary can be downloaded here, which can be remodeled to a minimal problematic environment. Attach the demo.zip to the comments.
Testtt.zip
I have a pod 'QSUtility', and 'QSUtility' have vendored_libraries 'libleveldb.a' 'libmemenv.a' 'libsnappy.a'.
When I embed 'QSUtility' to my project 'Testtt' with cocoapods, and build it, the 'libleveldb.a' 'libmemenv.a' 'libsnappy.a' will link to the QSUtility.framework.
But!
When I embed 'QSUtility' to my project 'Testtt' with cocoapods-binary, and build it, the 'libleveldb.a' 'libmemenv.a' 'libsnappy.a' will link to the Testtt project target.
I think the '.a' files should link into QSUtility.framework It seems some problem with vendored_libraries, could anyone please help me deal with it?
Thanks for your feedback!
If it's a bug:
What's your environment:
pod env | egrep 'CocoaPods |Xcode|cocoapods-binary'
then paste the result here CocoaPods : 1.8.4 Xcode : 11.2 (11B52) cocoapods-binary : 0.4.4A demo project is helpful: