use vendored_frameworks for Parse.framework, fixes for 0.38 cocoapods

[siuying]

Fixes the problem missing header in cocoapods 0.38

[segiddins]

@nlutsenko This look OK to you? 👍

This will fix CocoaPods/CocoaPods#3822

[nlutsenko]

Not sure, but I don't think so.
The tricky part is that we are shipping Static framework and want to surface both static and dynamic linking, for things like Swift projects.

By using this crazy thing - we can link as a framework and as a regular static pod.

[nlutsenko]

Also, latest is 1.7.5.1 (has the -ObjC linker flag forced)

[nlutsenko]

Found another way to fix this, but need a verification.

s.public_header_files = '*.h'
s.source_files = '*.h', 'Empty.m'
s.preserve_paths = 'Parse.framework/Parse'

s.vendored_library = 'libParse.a'
s.prepare_command = 'touch Empty.m && cp Parse.framework/Parse libParse.a && cp Parse.framework/Headers/* .'

@segiddins Does this look sane to you?

[nlutsenko]

Or actually just replacing public_header_files with s.public_header_files = 'Parse.framework/Headers/*.h' seems to work reliably.
I am wondering if glob expansion is just doing something weird...

[segiddins]

No, in 0.38 we only link Headers in .framework if it's a vendored framework to fix other issues. This hack that you're using is totally unsupported and iirc completely doesn't work in 0.38. The correct answer to support dylib usage is to ship a dynamic binary.

[nlutsenko]

Would any of the above solutions work for this? Shipping dynamic framework is not exactly an option right now... We will get there, but I would love to unbreak it for people even if it's a temporary solution.

[nlutsenko]

Ok, the hack above (cping headers from .framework) seems to actually work, since the headers are no longer in .framework :D
I am going to roll-forward the podspec.

[nlutsenko]

@siuying @dcow Would appreciate if you guys could verify that it works with pod 1.7.5.2

[ArtSabintsev]

👍 Would love to get feedback on this solution as well, as I'm currently going down the same path.

[roland9]

any updates - encountering the same issue here :(

[ArtSabintsev]

I originally came to this post attempting to solve this issue for other third-party static libs (not Parse). I was able to get it working by augmenting existing podspecs. Here's a tutorial I wrote about it: https://medium.com/@ArtSabintsev/importing-c-static-libraries-into-a-swift-project-using-cocoapods-a53993c3a2ca

[keith]

Any resolution to this?

[nlutsenko]

@keith Since now we are using completely different way of shipping (since we are open source), as well as podspec is very very different - I don't think this PR is relevant anymore, unless someone explicitly wants to use a 6 months old version of the framework.

[keith]

👍 closing