Podspec value for spec.libraries should not be added to OTHER_LIBTOOLFLAGS

[kanstantsin]

I've encountered an issue while building static library target which depends on a pod with dynamic library dependencies. That's needed for running tests on the library.
In this case cocoapods add these dynamic libraries flags to my static library's OTHER_LD_FLAGS which is copied to OTHER_LIBTOOLFLAGS, which produces errors like this:
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't locate file for: -lsqlite3
while build.

This happens because dynamic libraries should only be linked to the app, and should not be linked to static library.
So, values, specified in spec.libraries should go to OTHER_LD_FLAGS but not to OTHER_LIBTOOLFLAGS.

Here is the sample project to demonstrate the issue.
Replacing
pod 'AFNetworking'
with
pod 'AFNetworking', :podspec => '.'
and running pod install or pod update reproduces that.

[alloy]

Indeed. Is this something you will want to look into to create a patch for?

[alloy]

Looking back at the ticket that was about the need to specify OTHER_LIBTOOLFLAGS, it seems we should only need to specify the individual Pods targets there and any vendored_libraries (assuming they are static libraries).

[kanstantsin]

Sounds like a solution.
Unfortunately I'm not familiar to cocoapods project and not very good in ruby.
I've made a temporal workaround in my project by removing $(inherited) from OTHER_LD_FLAGS and specifying all of the pods flags manually.

It would be great if someone could fix that in a meantime.

[k0nserv]

I was looking briefly at this and it seems like it would require changing the way that Xcodeproj::Config works to differentiate between OTHER_LD_FLAGS and OTHER_LIBTOOLFLAGS

[themackworth]

@k0nserv Is that really need? I have no idea what I am doing, but would something like this work?
themackworth@29aed5c

[themackworth]

@alloy I was messing around with your suggestion this past thanksgiving break, and I ran into an issue with a few pods using your suggestion.

For example, the GoogleAds-IMA-iOS-SDK podspec doesn't use vendored_libraries but instead uses:

"preserve_paths": "GoogleIMASDK3/libGoogleIMA3.a",
"libraries": "GoogleIMA3",

This means that if you add only the pod target and vendored_libraries, then it won't link in their library. I assume that this is a bug in their podspec but I am sure others are doing it also.

[bamx23]

Will this issue be solved?

[segiddins]

This was fixed by #3677.