Deploying mobile apps / Deploying mobile apps on iOS devices |
The gmibuildtool is a utility to create and test applications for an iOS devices.
Option | Description |
---|---|
--app-name application-name |
Display name of the mobile app. This option can be specified to define the display name of the app, it sets the CFBundleDisplayName property in the Info.plist file. If not specified, the name defaults to "Noname". |
--app-version application-version |
Defines app version visible to the users on the App Store. This option is mandatory and sets CFBundleVersion properties in the Info.plist file. Note: If the --build-number option is not used,
--app-version will also set the both the
CFBundleShortVersionString property.
In iTunes Connect, you define the version of your app, that must match the CFBundleVersion property in the Info.plist file of the app. If these versions do not match, the app cannot be published. Once the app is visible on App Store, the version specified in iTunes Connect shows up in the "Version" section of the application page. The app version number should be a string comprised of three period-separated integers. For example: "1.4.2" |
--bundle-id bundle-identifier |
Defines the Bundle Identifier (a.k.a. App Id) for the app. This option is mandatory and sets the CFBundleIdentifier property in the Info.plist file. A bundle identifier is the unique identifier of your app, to let iOS recognize new app versions. When developing for the simulator, you can choose your own identifier. When creating an application for the App Store, the bundle identifier must be registered with Apple. If not specified, the name defaults to "noname" (for prototyping). |
--build-number build-number | Defines the build number used to upload a new binary of the same app version. This option must be used to distinguish different builds for the same app version. It sets the CFBundleShortVersionString property in the Info.plist file. The build number needs to be incremented in order to upload a new binary version of the same app version in iTunes Connect.If this option is not used, the build number defaults to the version specified with the --app-version option. The build number is a string comprised of three period-separated integers. For example: "1.4.2" |
--certificate identity |
Name of a certificate to sign the app. This option is mandatory to build apps for a physical device or for the app store. The certificate can be found in the Keychain access program, in the "Common Name" field of the certificate panel. The command security find-identity -v can be used to list all available certificates. |
--device device-name |
Defines the name of a device or simulator.
Note: Use the instruments -s XCode command to
find the list of available devices (simulators or connected
devices).
|
--help |
Display the help of the command tool. |
--icons icons-dir |
Provides the directory where the application icons are located. By default, the application icons directory is current-working-dir/gmi. The name of the app icon files must be: icon_57x57.png, icon_72x72.png, icon_29x29.png, icon_40x40.png, icon_120x120.png, icon_152x152.png, icon_58x58.png, icon_76x76.png, icon_80x80.png |
--launch-images launch-images-dir |
The directory where launch images are located. By default, the launch images directory is
current-working-dir/gmi.
Note: This
option is ignored if the --storyboard option is
provided.
The name of the image files must be: Default.png, Default@2x.png Default-568h@2x.png, Default-Portrait-667h@2x.png Default-Landscape-667h@2x.png, Default-Portrait-736h@3x.png, Default-Landscape-736h@3x.png, Default-Portrait.png, Default-Landscape.png Default-Portrait@2x.png, Default-Landscape@2x.png. Each file name corresponds to a device type (you may not need to provide all files if you target only recent iOS devices), see Apple Developer documentation for more details about launch images. |
--mode {debug|release} |
Controls the debug or release mode for the app. By default, the mode is debug. Note that the provisioning profile must correspond:
|
--output ipa-file-name |
Path to output IPA and APP files to be generated. By default, a "build" directory is created, with subdirectories containing the .ipa and .app files. An IPA file is created when building an application for a physical device and the App Store. The IPA file is not needed and will not be created when building for the simulator. |
--program-files program-dir |
Path to Genero BDL program files (.42m, .42f, etc). By default, the program files directory is the current work directory. Following files are automaticlly excluded: *.4gl, *.per, *.msg, *.str, *.sch, [Mm]akefile, *.42d, [Mm]akefile, *.[chdmo], *.xib, build/ (the build directory), gmi/ (this folder is the default location of LaunchScreens and AppIcons). If the file gmiignore exists, then this file contains additional files to be ignored. |
--provisioning provisioning-file |
Path to the provisioning profile (.mobileprovision). The provisioning profile is mandatory to build apps for a physical device or for the app store. Provisioning profiles can be found in $HOME/Library/MobileDevice/Provisioning\ Profiles/ |
--storyboard storyboard-file |
Path to the storyboard file, to get a splash screen to be displayed when the app starts. This file is an alternative for Launch Screens (--launch-images option). This option is mandatory if you do not provide launch images with the --launch-images option. The default storyboard is an empty screen. |