You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each target can declare one or more dependencies. See [Dependency](#dependency) for more info
96
+
Each target can declare one or more dependencies. See [Dependency](ProjectSpec.md#dependency) in the ProjectSpec for more info about all the properties
96
97
97
98
### Cocoapods
98
99
Use your `podfile` as normal. The pods themselves don't need to be referenced in the project spec. After you generate your project simply run `pod install` which will integrate with your project and create a workspace.
99
100
100
101
### Carthage
101
102
XcodeGen makes integrating Carthage dependencies super easy!
102
103
103
-
You simply reference them in each target that requires them and XcodeGen does the rest by automatically linking and embedding the carthage frameworks where neccessary.
104
+
You simply reference them in each target that requires them and XcodeGen does the rest by automatically linking and embedding the carthage frameworks where necessary.
104
105
105
106
```yaml
106
107
targets:
@@ -111,4 +112,29 @@ targets:
111
112
Framework:
112
113
dependencies:
113
114
- carthage: Alamofire
114
-
```
115
+
```
116
+
117
+
XcodeGen automatically creates the build phase that Carthage requires which lists all the files and runs `carthage copy-frameworks`. You can change the invocation of carthage to something different, for example if you are running it with [Mint](https://github.com/yonaskolb/mint). This is then prepended to ` copy frameworks`
118
+
119
+
```yaml
120
+
options:
121
+
carthageExecutablePath: mint run Carthage/Carthage carthage
122
+
```
123
+
124
+
By default XcodeGen looks for carthage frameworks in `Carthage/Build`. You can change this with the `carthageBuildPath` option
125
+
126
+
```yaml
127
+
options:
128
+
carthageBuildPath: ../../Carthage/Build
129
+
```
130
+
131
+
### SDK
132
+
System frameworks and libs can be linked by using the `sdk` dependency type. You can either specify frameworks or libs by using a `.framework` or `.tbd` filename, respectively
0 commit comments