| Updated: May 29, 2023 |
The qnxsoftwarecenter_clt script lets you run the QNX Software Center from the command line. The script uses the same infrastructure as the QNX Software Center’s GUI.
qnxsoftwarecenter_clt options
Microsoft Windows, Linux, macOS
The version number must contain four segments, separated by periods. The first three segments are numeric; the last segment is a string and typically specifies a date.
-fileInfo ~/qnx700/target/qnx7/aarch64le/lib/libcam.so
The query argument can specify one or more properties, expressed as field-value pairs:
property_name=value&property_name=value&...
Here are the supported properties:
| Property | Description |
|---|---|
| buildId | A unique ID, encoded in hex, that identifies the binary payload of the file. |
| digestSHA512 | A Secure Hash Algorithm 512-bit checksum, encoded in base64. |
| path | The partial or full path of the file. |
| packageId | The unique alphanumeric ID of the package to which the file belongs. |
| version | The version of the package to which the file belongs. |
| status | The software maturity of the file (either stable or experimental). |
The query argument also accepts parameters to control the sorting and pagination of output:
| Attribute | Description |
|---|---|
| sortOrder |
Use the specified list of comma-separated properties for sorting. The list can contain any of the properties in the table above. You can use the + and - characters to specify ascending and descending order, respectively. For instance: sortOrder=buildId+,path-,version+ |
| pageNo |
Return the specified page of results. If you omit pageSize, pageNo is ignored. |
| pageSize |
Print the specified number of results on each page. For instance, if you specify 5, each page will contain the results for 5 files. If you omit pageSize, the page size is unlimited. If you omit pageNo, pageSize is ignored. |
| details |
Print the details for each file on a separate row. For instance, if you specify details and the same file is found in two packages, the report will include two rows, one for each instance of the file. But if you omit details, the report will use one row for both files and collapse the column data. In that case, if any column value (for instance, packageId) differs between the two files, the report will present both values in the same cell. |
pageSize=100\&path=deva\*
Don't include any spaces in the argument.
If you wish to install multiple packages, specify all of them with a single -installPackage option. Don't use a separate -installPackage option for each package.
Here are some examples:
qnxsoftwarecenter_clt -listQuery 'Q:latest()'
qnxsoftwarecenter_clt -listQuery "Q:latest(x | x.id == 'com.qnx.sdp.target.screen.base')"
qnxsoftwarecenter_clt -listQuery "Q:select(x | x.id == 'com.qnx.sdp.target.screen.base')"
qnxsoftwarecenter_clt -listQuery "Q:latest(iu | iu.providedCapabilities.exists(p |
p.name == 'ifconfig'))"
Apply the specified report template to the manifest report.
| This template: | Lets you identify: |
|---|---|
| subsystem | Target subsystems that may require a production licensing agreement |
| packages | Properties (name, ID, version, etc.) of each file's parent package |
| targetscan | Path, size, architecture, build ID, parent package, and other properties of each file |
| notice | Various compliance properties (end-user license, OSS compliance, eligibility for redistribution, etc.) of each file |
| all | All available properties of each file |
Don't include any spaces in the argument.
If you wish to uninstall multiple packages, specify all of them with a single -uninstallPackage option. Don't use a separate -uninstallPackage option for each package.
The qnxsoftwarecenter_clt script lets you run the QNX Software Center from the command line. The script uses the same infrastructure as the QNX Software Center’s GUI: everything you do at the command line is reflected in the GUI, and vice versa. The script is located under the root of your hard drive in the \QNX\QNX Software Center directory (for instance, C:\QNX\QNX Software Center in Microsoft Windows).
myQNX authentication and cache synchronizationSeveral command-line options need to communicate with the remote myQNX server, including those that install or update packages, add or synchronize license keys, or activate products. When using any of these options, include the myQNX authentication options, -myqnx.user and -myqnx.password.
The -mirror option, which synchronizes the contents of your local cache with package metadata on the remote myQNX server, also requires the myQNX authentication options. You should use -mirror at least once before using options that need to communicate with the remote myQNX server. If you are writing installation scripts, avoid invoking -mirror multiple times as it can reduce performance significantly.
Installation directoryThe -destination option lets you specify the installation directory for any commands that install, uninstall, or query packages on disk. You must include it when using the -installBaseline option. In most cases, you need to use it only once, before calling -installBaseline. All subsequent commands will assume the same destination. You can omit -destination altogether if you work with only one installation. That said, we recommend that you always use it if you are writing scripts.
License keysBefore installing a licensed product, you must add the license key for that product. To add a license key manually, you can use -addLicenseKey, which also attempts to activate the product. Alternatively, you can use -syncLicenseKeys, which automatically synchronizes the license keys on your workstation with those deployed to you on the remote server. After using -syncLicenseKeys, use -activateAll to activate your products.
The qnxsoftwarecenter_clt script supports several options for working with patch sets, which allow you to install a specific set of products, patches, and updates. See “Export and import patch sets” for more information.
ProxiesIn most cases, you can ignore the proxy options. You need them only if your workstation sits behind a proxy server. If your proxy server supports HTTP and HTTPS, you can omit the http and https prefixes and issue a single set of proxy commands for both HTTP and HTTPS. Otherwise, issue a set of -http commands for HTTP and a separate set of -https commands for HTTPS.
If you encounter proxy connection issues, see the QNX Software Center Technotes: http://www.qnx.com/qsc_technotes.
ReportsThe qnxsoftwarecenter_clt script supports several options (-fileInfo, -fileSearch, -reportImportQScan, etc.) for creating manifest reports. These reports can help you perform compliance audits by indicating, for example, which subsystem a file belongs to, whether you can redistribute the file at runtime, or whether the file contains open source software. For information on using these options, see the individual option descriptions and the “Using the command line” section of the “Manifest Reports & File Lookup” chapter.
Directory structureThe QNX Software Center writes data to the following directories in your home directory:
| This directory: | Contains: |
|---|---|
| .qnx/swupdate/ | User settings and cache. |
| .qnx/swupdate/swupdate_profiles |
Package installation metadata. The QNX Software Center needs this directory to see your installations and installed packages. |
| .qnx/license/ |
Licenses for the QNX Software Development Platform (SDP) and other products. The QNX Software Center uses this directory to store information about your product activations; if anything happens to the directory, you’ll no longer be able to use the products. If this occurs, contact your license administrator, who can issue a special request to have your products deactivated (which will then allow you to reactivate them). |
| .qnx/qconfig/ | Metadata that the QNX Momentics IDE and other tools use to find the list of installed baseline packages. |