Lines Matching full:commandline
2 CommandLine 2.0 Library Manual
11 This document describes the CommandLine argument processing library. It will
12 show you how to use it, and what it can do. The CommandLine library uses a
20 CommandLine library to have the following features:
22 #. Speed: The CommandLine library is very quick and uses little resources. The
29 #. Type Safe: As a user of CommandLine, you don't have to worry about
34 #. No subclasses required: To use CommandLine, you instantiate variables that
45 #. Cleaner: CommandLine supports enum and other types directly, meaning that
50 #. Powerful: The CommandLine library supports many different types of arguments,
53 possible because CommandLine is...
55 #. Extensible: It is very simple to add a new argument type to CommandLine.
59 #. Labor Saving: The CommandLine library cuts down on the amount of grunt work
64 #. Capable: The CommandLine library can handle lots of different forms of
70 This document will hopefully let you jump in and start using CommandLine in your
77 This section of the manual runs through a simple CommandLine'ification of a
79 CommandLine library in your own program, and show you some of the cool things it
82 To start out, you need to include the CommandLine header file into your program:
86 #include "llvm/Support/CommandLine.h"
100 system which ones we want, and what type of arguments they are. The CommandLine
106 where to put the output. With the CommandLine library, this is represented like
119 "``cl::list``" template), and tell the CommandLine library that the data
156 argument, the CommandLine library allows for `positional`_ arguments to be
178 Again, the CommandLine library does not require the options to be specified in
185 By simply adding the `cl::Required`_ flag, the CommandLine library will
223 The CommandLine library uses a `different parser`_ for different data types.
271 the CommandLine library also provides primitives to support CommandLine option
321 So far we have seen how the CommandLine library handles builtin types like
336 "``compiler -O3 -O2``". The CommandLine library would not be able to catch
344 To cope with these problems, we can use an enum value, and have the CommandLine
368 with the "``clEnumValEnd``" argument!). The CommandLine library enforces that
469 processes the argument. The CommandLine library supports both forms so that you
531 `cl::OneOrMore`_ modifier to inform the CommandLine library that it is an error
593 program does. To add this to your CommandLine program, simply pass a third
601 cl::ParseCommandLineOptions(argc, argv, " CommandLine compiler example\n\n"
610 **OVERVIEW: CommandLine compiler example
646 OVERVIEW: This is a small program to demo the LLVM CommandLine API
675 Now that you know the basics of how to use the CommandLine library, this section
694 CommandLine library, this would be specified as:
828 CommandLine library, we would specify this as:
875 clients (requiring lots of .cpp files to ``#include CommandLine.h``).
1026 category. The CommandLine library specifies defaults for all of these settings
1059 value for this setting allows the CommandLine library to do error checking for
1101 value to be present. In the case of the CommandLine library, a value is either
1171 modifier added to allow the CommandLine library to recognize them. Note that
1184 The CommandLine library does not restrict how you use the **cl::Prefix** or
1189 To do this, the CommandLine library uses a greedy algorithm to parse the input
1268 Despite all of the built-in flexibility, the CommandLine option library really
1319 cl::ParseCommandLineOptions(argc, argv, "This is a small program to demo the LLVM CommandLine API");
1368 option instead of having the ``CommandLine`` library print out the usual version
1370 to use the ``CommandLine`` facilities. Such programs should just define a small
1525 CommandLine library uses an instance of ``parser<type>`` if the command line
1530 The CommandLine library provides the following builtin parser specializations,
1541 values, which allows you to use the CommandLine library for all of the error
1588 Although the CommandLine library has a lot of functionality built into it
1590 extensibility. This section discusses how the CommandLine library works under
1601 As `discussed previously`_, parsers are the portion of the CommandLine library
