@@ -21,10 +21,10 @@ In order to build the Zip file, you will need:
21
21
22
22
### Running the Tool
23
23
24
- You can run the tool with ` swift run zip-builder [ARGS] ` or generate an Xcode project with
25
- ` swift package generate-xcodeproj ` and run within Xcode.
24
+ You can run the tool with ` swift run zip-builder [ARGS] ` or ` open Package.swift ` to debug or run
25
+ within Xcode.
26
26
27
- Since Apple does not support linking libraries built by future Xcode versions, make sure to builid with the
27
+ Since Apple does not support linking libraries built by future Xcode versions, make sure to build with the
28
28
earliest Xcode needed by any of the library clients. The Xcode command line tools must also be configured
29
29
for that version. Check with ` xcodebuild -version ` .
30
30
@@ -69,7 +69,12 @@ Optional common arguments:
69
69
- ` --no-update-pod-repo `
70
70
- This is for speedups when ` pod repo update ` has already been run recently.
71
71
72
- For release engineers (Googlers packaging an upcoming Firebase release) these commands should also be used:
72
+ ### Firebase Release zip building
73
+
74
+ If the ` --zip-pods ` option is not specified, the tool will build a Firebase zip distribution.
75
+
76
+ For release engineers (Googlers packaging an upcoming Firebase release) these commands should also
77
+ be used:
73
78
- ` --custom-spec-repos sso://cpdc-internal/firebase `
74
79
- This pulls the latest podspecs from the CocoaPods staging area.
75
80
- ` --repo-dir path ` GitHub repo containing Template and Carthage json file inputs.
@@ -86,7 +91,7 @@ swift run zip-builder --update-pod-repo \
86
91
--keep-build-artifacts
87
92
```
88
93
89
- ### Carthage
94
+ #### Carthage
90
95
91
96
Carthage binaries can also be built at the same time as the zip file by passing in ` --enable-carthage-build `
92
97
as a command line argument. This directory should contain JSON files describing versions and download
0 commit comments