Create a runtime package
When you have completed your customization, you must build the GBC runtime package that includes your customization. Your Genero development team deploy this runtime package to their development or production environments.
If you are on Microsoft® Windows®, ensure you are using the legacy Command Prompt (cmd.exe) command-line utility to execute gbc instructions; do not use the Powershell command-line utility. If you are using a Genero Workplace Window, you are using the legacy Command Prompt (cmd.exe) command-line utility.
Building the package using default build
To produce a GBC runtime package using the settings of the custom.json file, execute:
$ gbc build --create-zip This command creates a zip file for the customization using the settings
of the compile.mode and
compile.customization parameters in
gbc-project-dir/custom.json.
Changing modes and customizations
To switch modes (cdev, dev,
prod), either change the
compile.mode parameter in custom.json or use the --compile-mode option of the gbc build command.
To replace the customization, either change the
compile.customization parameter in
custom.json or use the --customization option of the gbc build command.
This example specifies both a mode (prod) and a
customization (myCustomization):
gbc build --customization customization/myCustomization --compile-mode prod --create-zip Deploying the runtime package
The resulting GBC runtime package is located in gbc-project-dir/archive and takes the format:
fjs-gbc-version.suffix-buildbuildid-customization_customName.zipDeploy this package as you would deploy the runtime package provided by Four Js. See Deploy runtime on GAS.
You can rename this file with a name that is shorter and easier to manage.
To change the suffix used for a customization, see Change the version customization suffix.