QDK - QPKG Development Kit
  • Introduction
  • Installation of QDK
  • QPKG Configuration File
  • Installation Script
    • Generic Installation Script
    • Package Specific Installation Functions
    • Order of Execution
  • QDK Variables
  • Build Scripts
  • User Configuration File
  • Invoking qbuild
    • Initialize a Build Environment
    • Control the Build
    • Trust but Verify
    • Exclude Files
    • Scripts
    • Status Information
    • Sections
    • Extract QPKG Packages
    • Query Packages
    • Help and Usage
  • Creating a QPKG Package Using QDK
    • Creating a Simple QPKG Package
    • Creating Platform Specific QPKG Packages
    • Converting an Existing QPKG Package
  • Appendix A – QPKG Format
    • Header Script
    • Control Files
    • Data File
    • Extra Data Files
    • QDK Area
    • Tail Section
Powered by GitBook
On this page

Was this helpful?

Invoking qbuild

As the previous sections have shown, we can specify most options for each QPKG package in theconfiguration file and many times this is enough. But additionally, the qbuild application provides someglobal control through powerful command-line options and also a possibility to use different configurationsthat have been set up in the user configuration file.

The qbuild application has the following options

usage:

qbuild [--extract QPKG [DIR]] [--create-env NAME] [-s|--section SECTION]

[--root ROOT_DIR] [--build-arch ARCH] [--build-version VERSION]

[--build-number NUMBER] [--build-model MODEL] [--build-dir BUILD_DIR] [--force-config]

[--setup SCRIPT] [--teardown SCRIPT] [--pre-build SCRIPT]

[--post-build SCRIPT] [--exclude PATTERN] [--exclude-from FILE]

[--gzip|--bzip2|--7zip] [--sign] [--gpg-name ID] [--verify QPKG]

[--add-sign QPKG] [--import-key KEY] [--remove-key ID] [--list-keys]

[--query OPTION QPKG] [-v|--verbose] [-q|--quiet] [--strict]

[-?|-h|--help] [--usage] [-V|--version]

PreviousUser Configuration FileNextInitialize a Build Environment

Last updated 5 years ago

Was this helpful?