Home
QNX Software Center
The QNX Software Center (QSC) enables you to create and manage installations of the QNX Software Development Platform (SDP) and related products.
myQNX License Manager and QNX Software Center User's Guide
This guide explains how to use the myQNX License Manager and the QNX Software Center. It is intended for corporate buyers, development managers, and IT administrators who need to manage QNX product licenses, and for developers who need to install and maintain QNX software on their development hosts.
Glossary
To make best use of the QNX Software Center, we recommend that you become familiar with the following terms, which are used throughout the center's user interface and documentation.

QNX Software Center
The QNX Software Center (QSC) enables you to create and manage installations of the QNX Software Development Platform (SDP) and related products.
- myQNX License Manager and QNX Software Center User's Guide
  This guide explains how to use the myQNX License Manager and the QNX Software Center. It is intended for corporate buyers, development managers, and IT administrators who need to manage QNX product licenses, and for developers who need to install and maintain QNX software on their development hosts.
  - Introduction
    Together, the myQNX License Manager and the QNX Software Center make it easy to license, download, install, and maintain QNX software products. It doesn’t matter whether your company is a small development shop with a handful of developers or a large OEM with globally distributed software teams. Either way, these tools will maximize the efficiency of your license administrators and enable all of your developers to stay up to date with the latest QNX software tools and components.
  - Create Your myQNX Account
    To use the myQNX License Manager or the QNX Software Center, you must first create a myQNX account. Setup is easy and takes only a few minutes.
  - Important Terms and Definitions
    This section covers important definitions that can help you better understand how to use QNX licenses.
  - Using the myQNX License Manager
    The myQNX License Manager lets you take centralized control of the QNX licensing for your organization. It reduces the hard work of managing licenses for large software teams to a few simple tasks that you can perform from a single, easy-to-use control panel:
  - Using the QNX Software Center
    The QNX Software Center provides a secure, efficient way to discover, install, and manage software products distributed by BlackBerry QNX. It replaces traditional command-line procedures with a graphical user interface that takes the guesswork out of managing product dependencies. It also lets you create patch sets: specific configurations of QNX products, patches, and updates that enable development teams to reproduce issues and standardize on the same software base.
  - QNX Software Center Advanced Topics
    This chapter guides you through tasks that you may have to perform only on occasion. It also discusses how to address potential connectivity or license activation issues.
  - Using the QNX Software Center Command Line
    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.
  - Manifest Reports & File Lookup
    Using the QNX Software Center, you can create manifest reports for any QNX Software Development Platform (SDP) installation, or for any QNX target image that resides on your target hardware or development host.
  - Glossary
    To make best use of the QNX Software Center, we recommend that you become familiar with the following terms, which are used throughout the center's user interface and documentation.
- Creating and Deploying Installations of QNX SDP in Large Organizations
  This guide is intended for system administrators and developers who need to perform unattended installation of the QNX Software Center and the QNX Software Development Platform (SDP), or who need to create deployed installations of QNX SDP.
- Typographical Conventions, Support, and Licensing
  This section describes the typographical conventions used throughout the documentation and explains how to obtain technical support.

Glossary

To make best use of the QNX Software Center, we recommend that you become familiar with the following terms, which are used throughout the center's user interface and documentation.

Package: The minimal unit of software you can install. The QNX Software Center lets you work with a variety of package types, including baselines, board support packages (BSPs), patch sets, reference images, and source bundles. A package contains metadata (name, version, dependencies on other packages, etc.) and, in most cases, a payload of files.
Addon: An optional package that you can add to an installation.
Baseline: A package that serves as the basis of an installation; it must be installed before you can add any other packages (i.e. addons, updates) to the installation. A baseline has a name and a version, but has no dependencies on other packages.
Installation: Contains a baseline and any additional packages or updates that you’ve added to the baseline, all installed in a single directory tree. Your workstation can have multiple installations of the same or different baselines.
Package archive: Multiple packages packed into a single archive container such as .zip, .tar, .tar.gz, or .tar.xz. Typically used when you need to run the QNX Software Center offline.
Patch set: A package that acts like a recipe for installing packages. A patch set tells the QNX Software Center not only which packages to install, but also which version of each package to install. Patch sets enable all members of a team to standardize on the same software base; they also make it easier to reproduce issues across systems.
Repository: A database of software packages that the QNX Software Center uses to display the packages you can install or update.
Root package: A package that you've explicitly added to an installation (as opposed to a package that the QNX Software Center has installed to satisfy dependency requirements).
Status: The Status field identifies the maturity of the software at a file level, although it is usually defined at package level so that all included files have the same maturity. See Package status under Deploy licenses to users.

Page updated: September 05, 2024