Add dsym generation/export

[UnsafePointer]

Cocoapods Rome is a great alternative for Carthage if you depend on libraries that don't support Carthage yet and you'd like to avoid the CocoaPods integration with the user project. The only thing missing is that you can't debug the third party frameworks properly because the dSYM information is deleted after build and it defaults to "Release" configuration which has compiler optimisations that affect the debugger (wrong stepping and missing variable).

This PR includes the following:

• Exports the dSYM information per platforms somewhere accessible by the user project. You just need to add a run script phase with something like: cp -R "${SOURCE_ROOT}/third_party_dependencies/dSYM/${PLATFORM_NAME}"/* $BUILT_PRODUCTS_DIR to copy the output to the right place.
• Reads a environment variable to determine which configuration should be used to compile the frameworks. Not sure if there's a better way to pass parameters into a plugin, that'll be certainly ideal.

[Lascorbe]

Maybe you can add an opt-out parameter to do not link dSYM. I think there'll be way more people interested in having dSYM linked by default than the other way around. WDYT?

Thanks for the PR! 🍷

[BasThomas]

Are there any updates on this?

[orta]

OK, just looked this over, sorry for the year late review - but better than nothing.

There is a feature for cocoapods-plugins that allows passing options:

plugin 'cocoapods-rome',  {
  dsym: true,
  configuration: "Release"
}

maybe? ( you can see a usage example in https://github.com/CocoaPods/Rome/pull/61 )

This'll need docs, in the README - but conceptually I think it should get merged 👍

[UnsafePointer]

@orta thanks for the review! Agree, better than nothing 🎉

@Lascorbe @orta I included both of your comments, thank you.

[orta]

Cool, and I just merged another PR, so you have merge conflicts too ;)

[UnsafePointer]

@segiddins thanks for the review!

[orta]

Cool, yep, looks good to me