Add ability to pass in :products option to vendored Xcode projects

[chendo]

This PR adds the ability to specify a :products option to the Xcode vendor project type to match the :products option on static vendor projects.

Use case:
Cocoapods recently added dedicated targets for each pod (CocoaPods/CocoaPods#983) , then link it all together in libPods.a. However, RubyMotion attempts to -force_load in all the libraries found in the Pods build directory which includes all the libPods-RegexKitLite.a etc, so it ends up failing to link due to duplicate symbols.

I use the following with the patch below to fix the issue:

  app.vendor_project('Pods', :xcode,
                      :target        => 'Pods',
                      :products => ['libPods.a'])

[chendo]

This is still a problem for integrating with OS X projects using Cocoapods.

[alloy]

This looks good to me, I'll just have to test it manually first. Can you elaborate on how/why you need this on OS X specifically?

[chendo]

I’m using RubyMotion to test an Obj-C app that uses Cocoapods and I’m using the products to specify only to use the libPods.a file, otherwise it will try to include all the .a files compiled by CocoaPods and cause duplicate symbol issues. If there’s another way to solve this issue, I’d be happy to use that instead.

On Wednesday, 25 June 2014 at 5:17 am, Eloy Durán wrote:

This looks good to me, I'll just have to test it manually first. Can you elaborate on how/why you need this on OS X specifically?

—
Reply to this email directly or view it on GitHub (#119 (comment)).