gmibuildtool
The gmibuildtool is a utility to create and test applications for an iOS devices.
Syntax
gmibuildtool [options]
- options are described in Options.
Options
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 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
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
The recommendation for the app version number is that it is 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
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-cordova
cordova-plugin-names |
Defines Cordova plugins to be embedded in the app package. When specifying multiple cordova plugins, use the comma ( The name of the plugin must match the Git repository name. It is case-sensitive. Note: To get the list of available Cordova plugins, use the
gmibuildtool --list-plugins command.
|
--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 If this option is not used, the build number defaults to the version
specified with the 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. |
--crypto {yes|no} |
Enables GWS cryptographic APIs based on the OpenSSL library. When using this option, the OpenSSL library is embedded into the resulting .ipa file. The default is |
--device
device-name |
Defines the name of a device or simulator.
Note: Use the xcrun xctrace list devices Xcode® command to find the list of available
devices (simulators or connected devices).
|
--extension-libs |
Specify the libraries to use when compiling and linking the app. This option is used when you want to provide your own C extension or custom front calls. |
--help |
Displays options for the tool. |
--gbc
gbc-archive |
Defines the GBC to be used for Universal Rendering. |
--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: |
--install {yes|no} |
The The |
--install-plugins github-url |
This option installs additional plugins in the GMI installation directory. |
--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: 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. |
--list-plugins |
This option lists the shipped plugins and additional plugins installed in the GMI installation directory. |
--mode
{debug|release} |
Controls the debug or release mode for the app. By default, the mode is 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
( The default storyboard is showing an empty navigation bar and an empty toolbar. If the storyboard references images, gmibuildtool searches for the images in the same directory the storyboard is in, and bundles the images with the application. |
--update |
When installing with --install option on a simulator, the app
is first un-installed and then re-installed. Use --update to only update, and keep
the "Documents" dir (os.Path.pwd() ). When installing on a physical device, the app
is always updated (needs manual un-install to cleanup) |
--verbose
{yes|no} |
Enable the verbose mode. |
--version |
Displays version information. |