Helper for carthage related frameworks

[yonaskolb]

This would add an option to a carthage dependency that would copy all of its related frameworks as well.
This is for some carthage dependencies that actually have multiple frameworks you need to embed.

For example https://github.com/DaveWoodCom/XCGLogger requires that you embed both XCGLogger and ObjcExceptionBridging.
XcodeGen could read the file in Carthage/Build/.XCGLogger.version to extract all the required build artifacts:

{
  "commitish" : "6.1.0",
  "iOS" : [
    {
      "name" : "ObjcExceptionBridging",
      "hash" : "582b2059fd03bce0a3d265aa19d12915182be37e77e5d8502973766c9867cd9e"
    },
    {
      "name" : "XCGLogger",
      "hash" : "0736e85cd58080ece86985b85acb4c53bade7b849543e6d3b178d65f894f97b6"
    }
  ]
}

This functionality could live behind a flag. Something like the following:

old:

targets:
  Target:
    dependencies:
      - carthage: XCGLogger
      - carthage: ObjcExceptionBridging

new:

targets:
  Target:
    dependencies:
      - carthage: XCGLogger
        includeRelated: true

This behaviour could even be made the default but it would be a breaking change as sometimes you don't want to embed all of a dependencies frameworks

[AlexisQapa]

Awesome ! +1 for it becoming the default as most of the time you want to embed those.
For example when migrating Cocoapods project you have to figure out which lib depend on what

[rpassis]

@yonaskolb happy to take a stab at implementing this as it seems like it would be a useful feature.

[rpassis]

After a quick glance there are a few different ways we can do this but it's mainly down to 2 choices:

1. Include related dependencies during the parsing of the Target JSON/yaml file or;
2. Add a includeRelated property to Dependency and work out the related dependencies while generating the project inside PBXProjGenerator

Option 1 is a lot simpler and cleaner but feels a bit wrong for some reason. We will have to reach into the Carthage build folder to get the .version file during parsing, process it and then add the related dependencies while building the Target.

Option 2 will likely require changing logic related to carthage dependencies in a few different places.

Keen to hear your thoughts on this.
Rog

[yonaskolb]

That would be great if you want to work on this @rpassis!
I would vote for option 2. We have more information at that point, are working with proper types and can access options (There could be a top level option to opt in or out, as well as the finer grained per dependency control that would override this).

[yonaskolb]

This was added