|
|
3 jaren geleden | |
|---|---|---|
| .. | ||
| CarthageJSON | 2d51d693d5 Carthage 9.2.0 (#9931) | 3 jaren geleden |
| Sources | 2264982f76 Remove GoogleSignInSwift from binary distros (#9948) | 3 jaren geleden |
| Template | dc652459da Build zip with Xcode 13.3.1 (#9739) | 3 jaren geleden |
| DEVELOP.md | 4311d2906c Always build Carthage with Firebase zip distributions (#8098) | 4 jaren geleden |
| Package.swift | 38ac1bb382 Create a GitHub Action for Notices Generation. (#9657) | 3 jaren geleden |
| README.md | 56d2f1e022 Fix ZipBuilder option in README (#9141) | 4 jaren geleden |
| ZipBuilderV2Plan.md | cd3169739e Move zip-builder to ArgumentParser. (#6920) | 5 jaren geleden |
| ZipBuilderV3Plan.md | cd3169739e Move zip-builder to ArgumentParser. (#6920) | 5 jaren geleden |
This project includes Firebase release tooling including a zip builder and a Firebase release candidate creation tool.
The rest of this file documents using the zip-builder tool. Information about the rest of the
tools for managing Firebase releases and information about developing these tools is at
DEVELOP.md
The zip-builder tool generates a zip distribution of binary .xcframeworks from an input set of
CocoaPods.
In order to build the Zip file, you will need:
You can run the tool with swift run zip-builder [ARGS] or open Package.swift to debug or run
within Xcode.
Since Apple does not support linking libraries built by future Xcode versions, make sure to build with the
earliest Xcode needed by any of the library clients. The Xcode command line tools must also be configured
for that version. Check with xcodebuild -version.
See main.swift for information on specific launch arguments, or use swift run zip-builder --help.
You can pass in launch arguments with Xcode by clicking "zip-builder" beside the Run/Stop buttons, clicking "Edit Scheme" and adding them in the "Arguments Passed On Launch" section.
Use --pods <pods> to specify the CocoaPods to build.
The pods option will choose whatever pods get installed from an unversioned CocoaPods install,
typically the latest versions.
To explicitly specify the CocoaPods versions, use a JSON specification :
--zip-pods <PATH_TO.json>
This is a JSON list of the pods to consolidate into a zip of binary frameworks. For example,
[
{
"name": "GoogleDataTransport",
"version" : "3.2.0"
},
{
"name": "FirebaseMessaging"
}
]
Indicates to install the version 3.2.0 of "GoogleDataTransport" and the latest version of "FirebaseMessaging". The version string is optional and can be any valid CocoaPods Podfile version specifier.
Other optional arguments:
--no-update-pod-repo
pod repo update has already been run recently.--minimum-ios-version <minimum-ios-version>
--output-dir <output-dir>
--keep-build-artifacts