QCommandLineParser Class

The QCommandLineParser class provides a means for handling the command line options. More...

Header: #include <QCommandLineParser>
qmake: QT += core
Since: Qt 5.2

This class was introduced in Qt 5.2.

Public Types

enum OptionsAfterPositionalArgumentsMode { ParseAsOptions, ParseAsPositionalArguments }
enum SingleDashWordOptionMode { ParseAsCompactedShortOptions, ParseAsLongOptions }

Detailed Description

QCoreApplication provides the command-line arguments as a simple list of strings. QCommandLineParser provides the ability to define a set of options, parse the command-line arguments, and store which options have actually been used, as well as option values.

Any argument that isn't an option (i.e. doesn't start with a -) is stored as a "positional argument".

The parser handles short names, long names, more than one name for the same option, and option values.

Options on the command line are recognized as starting with a single or double - character(s). The option - (single dash alone) is a special case, often meaning standard input, and not treated as an option. The parser will treat everything after the option -- (double dash) as positional arguments.

Short options are single letters. The option v would be specified by passing -v on the command line. In the default parsing mode, short options can be written in a compact form, for instance -abc is equivalent to -a -b -c. The parsing mode for can be set to ParseAsLongOptions, in which case -abc will be parsed as the long option abc.

Long options are more than one letter long and cannot be compacted together. The long option verbose would be passed as --verbose or -verbose.

Passing values to options can be done using the assignment operator: -v=value --verbose=value, or a space: -v value --verbose value, i.e. the next argument is used as value (even if it starts with a -).

The parser does not support optional values - if an option is set to require a value, one must be present. If such an option is placed last and has no value, the option will be treated as if it had not been specified.

The parser does not automatically support negating or disabling long options by using the format --disable-option or --no-option. However, it is possible to handle this case explicitly by making an option with no-option as one of its names, and handling the option explicitly.

Example:

 int main(int argc, char *argv[])
 {
     QCoreApplication app(argc, argv);
     QCoreApplication::setApplicationName("my-copy-program");
     QCoreApplication::setApplicationVersion("1.0");

     QCommandLineParser parser;
     parser.setApplicationDescription("Test helper");
     parser.addHelpOption();
     parser.addVersionOption();
     parser.addPositionalArgument("source", QCoreApplication::translate("main", "Source file to copy."));
     parser.addPositionalArgument("destination", QCoreApplication::translate("main", "Destination directory."));

     // A boolean option with a single name (-p)
     QCommandLineOption showProgressOption("p", QCoreApplication::translate("main", "Show progress during copy"));
     parser.addOption(showProgressOption);

     // A boolean option with multiple names (-f, --force)
     QCommandLineOption forceOption(QStringList() << "f" << "force",
             QCoreApplication::translate("main", "Overwrite existing files."));
     parser.addOption(forceOption);

     // An option with a value
     QCommandLineOption targetDirectoryOption(QStringList() << "t" << "target-directory",
             QCoreApplication::translate("main", "Copy all source files into <directory>."),
             QCoreApplication::translate("main", "directory"));
     parser.addOption(targetDirectoryOption);

     // Process the actual command line arguments given by the user
     parser.process(app);

     const QStringList args = parser.positionalArguments();
     // source is args.at(0), destination is args.at(1)

     bool showProgress = parser.isSet(showProgressOption);
     bool force = parser.isSet(forceOption);
     QString targetDir = parser.value(targetDirectoryOption);
     // ...
 }

If your compiler supports the C++11 standard, the three addOption() calls in the above example can be simplified:

     parser.addOptions({
         // A boolean option with a single name (-p)
         {"p",
             QCoreApplication::translate("main", "Show progress during copy")},
         // A boolean option with multiple names (-f, --force)
         {{"f", "force"},
             QCoreApplication::translate("main", "Overwrite existing files.")},
         // An option with a value
         {{"t", "target-directory"},
             QCoreApplication::translate("main", "Copy all source files into <directory>."),
             QCoreApplication::translate("main", "directory")},
     });

Known limitation: the parsing of Qt options inside QCoreApplication and subclasses happens before QCommandLineParser exists, so it can't take it into account. This means any option value that looks like a builtin Qt option, will be treated by QCoreApplication as a builtin Qt option. Example: --profile -reverse will lead to QGuiApplication seeing the -reverse option set, and removing it from QCoreApplication::arguments() before QCommandLineParser defines the profile option and parses the command line.

How to Use QCommandLineParser in Complex Applications

In practice, additional error checking needs to be performed on the positional arguments and option values. For example, ranges of numbers should be checked.

It is then advisable to introduce a function to do the command line parsing which takes a struct or class receiving the option values returning an enumeration representing the result. The dnslookup example of the QtNetwork module illustrates this:

 struct DnsQuery
 {
     DnsQuery() : type(QDnsLookup::A) {}

     QDnsLookup::Type type;
     QHostAddress nameServer;
     QString name;
 };

 enum CommandLineParseResult
 {
     CommandLineOk,
     CommandLineError,
     CommandLineVersionRequested,
     CommandLineHelpRequested
 };

 CommandLineParseResult parseCommandLine(QCommandLineParser &parser, DnsQuery *query, QString *errorMessage)
 {
     parser.setSingleDashWordOptionMode(QCommandLineParser::ParseAsLongOptions);
     const QCommandLineOption nameServerOption("n", "The name server to use.", "nameserver");
     parser.addOption(nameServerOption);
     const QCommandLineOption typeOption("t", "The lookup type.", "type");
     parser.addOption(typeOption);
     parser.addPositionalArgument("name", "The name to look up.");
     const QCommandLineOption helpOption = parser.addHelpOption();
     const QCommandLineOption versionOption = parser.addVersionOption();

     if (!parser.parse(QCoreApplication::arguments())) {
         *errorMessage = parser.errorText();
         return CommandLineError;
     }

     if (parser.isSet(versionOption))
         return CommandLineVersionRequested;

     if (parser.isSet(helpOption))
         return CommandLineHelpRequested;

     if (parser.isSet(nameServerOption)) {
         const QString nameserver = parser.value(nameServerOption);
         query->nameServer = QHostAddress(nameserver);
         if (query->nameServer.isNull() || query->nameServer.protocol() == QAbstractSocket::UnknownNetworkLayerProtocol) {
             *errorMessage = "Bad nameserver address: " + nameserver;
             return CommandLineError;
         }
     }

     if (parser.isSet(typeOption)) {
         const QString typeParameter = parser.value(typeOption);
         const int type = typeFromParameter(typeParameter.toLower());
         if (type < 0) {
             *errorMessage = "Bad record type: " + typeParameter;
             return CommandLineError;
         }
         query->type = static_cast<QDnsLookup::Type>(type);
     }

     const QStringList positionalArguments = parser.positionalArguments();
     if (positionalArguments.isEmpty()) {
         *errorMessage = "Argument 'name' missing.";
         return CommandLineError;
     }
     if (positionalArguments.size() > 1) {
         *errorMessage = "Several 'name' arguments specified.";
         return CommandLineError;
     }
     query->name = positionalArguments.first();

     return CommandLineOk;
 }

In the main function, help should be printed to the standard output if the help option was passed and the application should return the exit code 0.

If an error was detected, the error message should be printed to the standard error output and the application should return an exit code other than 0.

     QCoreApplication::setApplicationVersion(QT_VERSION_STR);
     QCoreApplication::setApplicationName(QCoreApplication::translate("QDnsLookupExample", "DNS Lookup Example"));
     QCommandLineParser parser;
     parser.setApplicationDescription(QCoreApplication::translate("QDnsLookupExample", "An example demonstrating the class QDnsLookup."));
     DnsQuery query;
     QString errorMessage;
     switch (parseCommandLine(parser, &query, &errorMessage)) {
     case CommandLineOk:
         break;
     case CommandLineError:
         fputs(qPrintable(errorMessage), stderr);
         fputs("\n\n", stderr);
         fputs(qPrintable(parser.helpText()), stderr);
         return 1;
     case CommandLineVersionRequested:
         printf("%s %s\n", qPrintable(QCoreApplication::applicationName()),
                qPrintable(QCoreApplication::applicationVersion()));
         return 0;
     case CommandLineHelpRequested:
         parser.showHelp();
         Q_UNREACHABLE();
     }

A special case to consider here are GUI applications on Windows and mobile platforms. These applications may not use the standard output or error channels since the output is either discarded or not accessible.

On Windows, QCommandLineParser uses message boxes to display usage information and errors if no console window can be obtained.

For other platforms, it is recommended to display help texts and error messages using a QMessageBox. To preserve the formatting of the help text, rich text with <pre> elements should be used:

 switch (parseCommandLine(parser, &query, &errorMessage)) {
 case CommandLineOk:
     break;
 case CommandLineError:
     QMessageBox::warning(0, QGuiApplication::applicationDisplayName(),
                          "<html><head/><body><h2>" + errorMessage + "</h2><pre>"
                          + parser.helpText() + "</pre></body></html>");
     return 1;
 case CommandLineVersionRequested:
     QMessageBox::information(0, QGuiApplication::applicationDisplayName(),
                              QGuiApplication::applicationDisplayName() + ' '
                              + QCoreApplication::applicationVersion());
     return 0;
 case CommandLineHelpRequested:
     QMessageBox::warning(0, QGuiApplication::applicationDisplayName(),
                          "<html><head/><body><pre>"
                          + parser.helpText() + "</pre></body></html>");
     return 0;
 }

However, this does not apply to the dnslookup example, because it is a console application.

See also QCommandLineOption and QCoreApplication.

Member Type Documentation

enum QCommandLineParser::OptionsAfterPositionalArgumentsMode

This enum describes the way the parser interprets options that occur after positional arguments.

ConstantValueDescription
QCommandLineParser::ParseAsOptions0application argument --opt -t is interpreted as setting the options opt and t, just like application --opt -t argument would do. This is the default parsing mode. In order to specify that --opt and -t are positional arguments instead, the user can use --, as in application argument -- --opt -t.
QCommandLineParser::ParseAsPositionalArguments1application argument --opt is interpreted as having two positional arguments, argument and --opt. This mode is useful for executables that aim to launch other executables (e.g. wrappers, debugging tools, etc.) or that support internal commands followed by options for the command. argument is the name of the command, and all options occurring after it can be collected and parsed by another command line parser, possibly in another executable.

This enum was introduced or modified in Qt 5.6.

See also setOptionsAfterPositionalArgumentsMode().

enum QCommandLineParser::SingleDashWordOptionMode

This enum describes the way the parser interprets command-line options that use a single dash followed by multiple letters, as as -abc.

ConstantValueDescription
QCommandLineParser::ParseAsCompactedShortOptions0-abc is interpreted as -a -b -c, i.e. as three short options that have been compacted on the command-line, if none of the options take a value. If a takes a value, then it is interpreted as -a bc, i.e. the short option a followed by the value bc. This is typically used in tools that behave like compilers, in order to handle options such as -DDEFINE=VALUE or -I/include/path. This is the default parsing mode. New applications are recommended to use this mode.
QCommandLineParser::ParseAsLongOptions1-abc is interpreted as --abc, i.e. as the long option named abc. This is how Qt's own tools (uic, rcc...) have always been parsing arguments. This mode should be used for preserving compatibility in applications that were parsing arguments in such a way. There is an exception if the a option has the QCommandLineOption::ShortOptionStyle flag set, in which case it is still interpreted as -a bc.

See also setSingleDashWordOptionMode().