Automation tool to bind CocoaPods to NuGet packages for Xamarin.iOS
F# Objective-C Other
Latest commit 38a9ed5 Feb 7, 2017 @alexsorokoletov committed on GitHub Update README.md

README.md

Automatic way of binding Firebase pods for Xamarin iOS

Join the chat at https://gitter.im/objc-automatic/Lobby

Automatic conversion from cocoapod to nuget (saving the hierarchy). For example, the tool provides "automatic" way to bind all the pods for Firebase iOS for Xamarin. Project is in alpha state, expect all nuget packages of Firebase in the Nuget feed soon in alpha channel.

Tool works as a two step process. First you generate the bindings automatically (via bind.sh ) then you compile the bindings and package then as nuget.

To some extent this tool is similar to Xamarin's Objective Sharpie. Biggest difference is that this tool works with CocoaPod hierachy and generates set of dependent packages with Xamarin.iOS bindings mimicking hierarchy of CocoaPod

How to use

Blog post explaining whole story: Easy way to create Xamarin.iOS binding from CocoaPods

Video 1. objc-automatic generating lottie-ios binding for Xamarin.iOS

Video 2. objc-automatic demo - binding Firebase/Analytics to Xamarin

Video 3. objc-automatic overview and details how it works internally

Prerequisites:

  • CocoaPods (Getting started guide). One might need pod try yourpodname at least once to force CocoaPods to update local specs repo.
  • run mozroots --import --sync to import SSL root certificates.
  • NuGet 3. To update NuGet, run sudo nuget update -Self
  • Xamarin iOS
  • ObjectiveSharpie. Download information and manual.

First stage - generate bindings

To generate bindings sh bind.sh POD=FirebaseDatabase or sh bind.sh POD=Firebase/Messaging or use other pod names (see here https://firebase.google.com/docs/ios/setup in Available Pods section)

Other options:

  • POD=podName
  • VERSION=version (override versions in all packages --- use with caution and for tests)
  • SINGLE=yes - do not take into consideration pod references
  • VERSION-TYPE=-beta (adds suffix to version)
  • VERBOSE - to enable verbose output

Second stage - compile and package as nuget To compile bindings and package then, run sh FirebaseDatabase.build.sh script in the bindings folder. This script is generated automatically and will show any errors in the bindings you need to correct.

After 2nd stage you should have a set of nuget packages ready for publishing in folder bindings/packages-raw

Between 1st and 2nd stages you might need to check generated bindings and make sure they compile. With git diff this is usually quick and easy.

Building generated bindings

  1. To build all bindings use sh {pod name}.build.sh script in bindings folder.
  2. To compile single binding use msbuild -p:Configuration=Release to compile in Release in the specific binding folder (e.g. bindings/AWSCore)

Additional options

Clean bindings folder - sh bind.sh CleanBindings

Clean pods folder - sh bind.sh CleandPods

Things to fix and improve

  1. detailed nuspec packages info and support for sub-version updates
  2. support weak_frameworks linker flag
  3. way to generate multiple pods at once
  4. support for iOS flavored dependencies (see ZendeskSDK pod)
  5. video showing how to use this

Contribution

Please ping me if you want to collaborate, extend, fix or change the project. I will be happy to sort out the process and answer any questions

Extra

Please see beginning of the build.fsx file for configuration options (verbose logs, versions, etc)

Pods to try

AWSCognito, Facebook Pop, Firebase *, GoogleFontsiOS