@@ -30,21 +30,22 @@ for that version. Check with `xcodebuild -version`.
30
30
31
31
### Launch Arguments
32
32
33
- See ` main.swift ` and the ` LaunchArgs ` struct for information on specific launch arguments.
33
+ See ` main.swift ` for information on specific launch arguments, or use ` swift run zip-builder --help ` .
34
34
35
- You can pass in launch arguments with Xcode by clicking "zip-builder" beside the Run/Stop buttons, clicking "Edit
36
- Scheme" and adding them in the "Arguments Passed On Launch" section.
35
+ You can pass in launch arguments with Xcode by clicking "zip-builder" beside the Run/Stop buttons, clicking
36
+ "Edit Scheme" and adding them in the "Arguments Passed On Launch" section.
37
37
38
38
#### Common Arguments
39
39
40
40
These arguments assume you're running the command from the ` ReleaseTooling ` directory.
41
41
42
42
** Required** arguments:
43
- - ` -templateDir $(pwd)/Template `
44
- - This should always be the same.
43
+
44
+ - ` --repo-dir <PATH_TO_firebase_ios_sdk_REPO> `
45
+ - The root of the ` firebase-ios-sdk ` repo.
45
46
46
47
Typical argument (all use cases except Firebase release build):
47
- - ` -zipPods <PATH_TO.json> `
48
+ - ` --zip-pods <PATH_TO.json> `
48
49
- This is a JSON list of the pods to consolidate into a zip of binary frameworks. For example,
49
50
50
51
```
@@ -65,32 +66,32 @@ valid [CocoaPods Podfile version specifier](https://guides.cocoapods.org/syntax/
65
66
66
67
67
68
Optional common arguments:
68
- - ` -updatePodRepo false `
69
+ - ` --no-update-pod-repo `
69
70
- This is for speedups when ` pod repo update ` has already been run recently.
70
71
71
72
For release engineers (Googlers packaging an upcoming Firebase release) these commands should also be used:
72
- - ` -customSpecRepos sso://cpdc-internal/firebase `
73
+ - ` --custom-spec-repos sso://cpdc-internal/firebase `
73
74
- This pulls the latest podspecs from the CocoaPods staging area.
74
- - ` -repoDir path ` GitHub repo containing Template and Carthage json file inputs.
75
- - ` -carthageBuild true ` Turns on generation of Carthage zips and json file updates.
76
- - ` -keepBuildArtifacts true ` Useful for debugging and verifying the zip build contents.
75
+ - ` --repo-dir path ` GitHub repo containing Template and Carthage json file inputs.
76
+ - ` --enable-carthage-build ` Turns on generation of Carthage zips and json file updates.
77
+ - ` --keep-build-artifacts ` Useful for debugging and verifying the zip build contents.
77
78
78
79
Putting them all together, here's a common command to build a releaseable Zip file:
79
80
80
81
```
81
- swift run zip-builder -updatePodRepo true \
82
- -repoDir <PATH_TO_current.firebase_ios_sdk.repo> \
83
- -customSpecRepos sso://cpdc-internal/firebase
84
- -carthageBuild true
85
- -keepBuildArtifacts true
82
+ swift run zip-builder --update-pod-repo \
83
+ --repo-dir <PATH_TO_current.firebase_ios_sdk.repo> \
84
+ --custom-spec-repos sso://cpdc-internal/firebase \
85
+ --enable-carthage-build \
86
+ --keep-build-artifacts
86
87
```
87
88
88
89
### Carthage
89
90
90
- Carthage binaries can also be built at the same time as the zip file by passing in `-carthageBuild
91
- true` as a command line argument. This directory should contain JSON files describing versions
92
- and download locations for each product. This will result in a folder called "carthage" at the root where the zip
93
- directory exists containing all the zip files and JSON files necessary for distribution.
91
+ Carthage binaries can also be built at the same time as the zip file by passing in ` --enable-carthage-build `
92
+ as a command line argument. This directory should contain JSON files describing versions and download
93
+ locations for each product. This will result in a folder called "carthage" at the root where the zip directory exists
94
+ containing all the zip files and JSON files necessary for distribution.
94
95
95
96
## Firebase Releaser
96
97
@@ -99,11 +100,11 @@ for the process documentation.
99
100
100
101
### Launch Arguments
101
102
102
- See ` main.swift ` and the ` LaunchArgs ` struct for information on specific launch arguments.
103
+ See ` main.swift ` for information on specific launch arguments.
103
104
104
105
You can pass in launch arguments with Xcode by selecting the "firebase-releaser" scheme
105
- beside the Run/Stop buttons, clicking "Edit
106
- Scheme" and adding them in the "Arguments Passed On Launch" section.
106
+ beside the Run/Stop buttons, clicking "Edit Scheme" and adding them in the "Arguments Passed On Launch"
107
+ section.
107
108
108
109
## Development Philosophy
109
110
0 commit comments