Add ability to store prebuilt frameworks in shared cache folder

[Rag0n]

Resolves #37

[leavez]

Thank for the new feature implementation. But a fundamental question: How to identify the pod and its generated framework? There may be code in podfile to modify the generated pod targets, and it will lead to different build result.

[Rag0n]

I don't understand your point. Could you provide a use case? I mean what do you want to modify in prebuilt framework? Cache is respecting custom build options set via set_custom_xcodebuild_options_for_prebuilt_frameworks. I don't see difference between using cache and not using it, probably I'm missing something.

[jaximan]

I guess case is when Podfile contains :binary => true only for few targets, not all of them. @Rag0n Thank you for this! Mind if I collaborate with you and add s3 remote cache on top of your implementation. My case is, having > 10 build machines and build/collect cache for frameworks on all of them is waste of resources.

[Rag0n]

But cache only works for :binary => true pods. Do you think we should add another flag to control cache behaviour for individual pods? From my point of you it's useless.

I would like to have S3 remote cache as well. @jaximan, do you want to implement it by yourself or you need some help?

[jaximan]

@Rag0n I can add it, would you like to have PR for your branch or as separate PR for this master after your change is merged?

[Rag0n]

I think PR for this branch will be faster, but it's up to you.

[jaximan]

Good day @leavez
I'm wondering, if you could review changes or assign someone?

[acecilia]

What is needed for this PR to move forward?

[isnine]

@Rag0n Hello,I like this feature very much, but I tried it and there seems to be some problems

NoMethodError - undefined methodhas_local_cache_for' for Pod::Prebuild::SharedCache:Class
Did you mean? has_local_cache_for?
/Users/nine/work/bytedance/cocoapods-binary/lib/cocoapods-binary/helper/shared_cache.rb:16:in has?'