I found how to print "complete usage" of
There's nothing in the Apple's document related to that.
What is xcodebuild?
On Terminal.app, run the following:
$ xcodebuild -help
Printing Complete Usage
Usage: xcodebuild [-project <projectname>] [[-target <targetname>]...|-alltargets] [-configuration <configurationname>] [-arch <architecture>]... [-sdk [<sdkname>|<sdkpath>]] [-showBuildSettings] [<buildsetting>=<value>]... [<buildaction>]... xcodebuild [-project <projectname>] -scheme <schemeName> [-destination <destinationspecifier>]... [-configuration <configurationname>] [-arch <architecture>]... [-sdk [<sdkname>|<sdkpath>]] [-showBuildSettings] [<buildsetting>=<value>]... [<buildaction>]... xcodebuild -workspace <workspacename> -scheme <schemeName> [-destination <destinationspecifier>]... [-configuration <configurationname>] [-arch <architecture>]... [-sdk [<sdkname>|<sdkpath>]] [-showBuildSettings] [<buildsetting>=<value>]... [<buildaction>]... xcodebuild -version [-sdk [<sdkfullpath>|<sdkname>] [<infoitem>] ] xcodebuild -list [[-project <projectname>]|[-workspace <workspacename>]] xcodebuild -showsdks xcodebuild -exportArchive -archivePath <xcarchivepath> -exportPath <destinationpath> -exportOptionsPlist <plistpath> xcodebuild -exportLocalizations -localizationPath <path> -project <projectname> [-exportLanguage <targetlanguage>...] xcodebuild -importLocalizations -localizationPath <path> -project <projectname> Options: -usage print brief usage -help print complete usage -verbose provide additional status output -license show the Xcode and SDK license agreements -checkFirstLaunchStatus Check if any First Launch tasks need to be performed -project NAME build the project NAME -target NAME build the target NAME -alltargets build all targets -workspace NAME build the workspace NAME -scheme NAME build the scheme NAME -configuration NAME use the build configuration NAME for building each target -xcconfig PATH apply the build settings defined in the file at PATH as overrides -arch ARCH build each target for the architecture ARCH; this will override architectures defined in the project -sdk SDK use SDK as the name or path of the base SDK when building the project -toolchain NAME use the toolchain with identifier or name NAME -destination DESTINATIONSPECIFIER use the destination described by DESTINATIONSPECIFIER (a comma-separated set of key=value pairs describing the destination to use) -destination-timeout TIMEOUT wait for TIMEOUT seconds while searching for the destination device -parallelizeTargets build independent targets in parallel -jobs NUMBER specify the maximum number of concurrent build operations -dry-run do everything except actually running the commands -hideShellScriptEnvironment don't show shell script environment variables in build log -showsdks display a compact list of the installed SDKs -showBuildSettings display a list of build settings and values -list lists the targets and configurations in a project, or the schemes in a workspace -find-executable NAME display the full path to executable NAME in the provided SDK and toolchain -find-library NAME display the full path to library NAME in the provided SDK and toolchain -version display the version of Xcode; with -sdk will display info about one or all installed SDKs -enableAddressSanitizer YES|NO turn the address sanitizer on or off when testing -resultBundlePath PATH specifies the directory where a result bundle describing what occurred will be placed -derivedDataPath PATH specifies the directory where build products and other derived data will go -archivePath PATH specifies the directory where any created archives will be placed, or the archive that should be exported -exportArchive specifies that an archive should be exported -exportOptionsPlist PATH specifies a path to a plist file that configures archive exporting -enableCodeCoverage YES|NO turn code coverage on or off when testing -exportPath PATH specifies the destination for the product exported from an archive -skipUnavailableActions specifies that scheme actions that cannot be performed should be skipped instead of causing a failure -exportLocalizations exports completed and outstanding project localizations -importLocalizations imports localizations for a project, assuming any necessary localized resources have been created in Xcode -localizationPath specifies a path to XLIFF localization files -exportLanguage specifies multiple optional ISO 639-1 languages included in a localization export Available keys for -exportOptionsPlist: compileBitcode : Bool For non-App Store exports, should Xcode re-compile the app from bitcode? Defaults to YES. embedOnDemandResourcesAssetPacksInBundle : Bool For non-App Store exports, if the app uses On Demand Resources and this is YES, asset packs are embedded in the app bundle so that the app can be tested without a server to host asset packs. Defaults to YES unless onDemandResourcesAssetPacksBaseURL is specified. iCloudContainerEnvironment For non-App Store exports, if the app is using CloudKit, this configures the "com.apple.developer.icloud-container-environment" entitlement. Available options: Development and Production. Defaults to Development. manifest : Dictionary For non-App Store exports, users can download your app over the web by opening your distribution manifest file in a web browser. To generate a distribution manifest, the value of this key should be a dictionary with three sub-keys: appURL, displayImageURL, fullSizeImageURL. The additional sub-key assetPackManifestURL is required when using on demand resources. method : String Describes how Xcode should export the archive. Available options: app-store, package, ad-hoc, enterprise, development, and developer-id. The list of options varies based on the type of archive. Defaults to development. onDemandResourcesAssetPacksBaseURL : String For non-App Store exports, if the app uses On Demand Resources and embedOnDemandResourcesAssetPacksInBundle isn't YES, this should be a base URL specifying where asset packs are going to be hosted. This configures the app to download asset packs from the specified URL. teamID : String The Developer Portal team to use for this export. Defaults to the team used to build the archive. thinning : String For non-App Store exports, should Xcode thin the package for one or more device variants? Available options: <none> (Xcode produces a non-thinned universal app), <thin-for-all-variants> (Xcode produces a universal app and all available thinned variants), or a model identifier for a specific device (e.g. "iPhone7,1"). Defaults to <none>. uploadBitcode : Bool For App Store exports, should the package include bitcode? Defaults to YES. uploadSymbols : Bool For App Store exports, should the package include symbols? Defaults to YES.