Lines Matching full:specify
36 #. Globally accessible: Libraries can specify command line arguments that are
53 Simply specify the parser that you want to use with the command line option
102 we would like to support the Unix-standard '``-o <filename>``' option to specify
111 cl::opt<string> OutputFilename("o", cl::desc("Specify output filename"), cl::value_desc("filename"));
114 result of the "``o``" argument (first parameter). We specify that this is a
119 The second and third parameters (which are optional) are used to specify what to
129 -o <filename> - Specify output filename
163 as the input filename. Here we use the `cl::init`_ option to specify an initial
165 (if you do not specify a `cl::init`_ modifier for an option, then the default
168 always specify an input filename, we would add the `cl::Required`_ flag, and we
195 -o <filename> - Specify output filename
310 ... which is much nicer! The "`cl::alias`_" can be used to specify an
322 The answer is that it uses a table-driven generic parser (unless you specify
332 #. A user could specify more than one of the options at a time, for example,
366 the user can only specify one of the options, and it ensure that only valid enum
383 -o <filename> - Specify output filename
409 specify the name that the flag should get. In general a direct mapping is nice,
417 style in our compiler to specify different debug levels that can be used.
422 optimization level flags, but we also specify an option name. For this case,
460 -o <filename> - Specify output filename
529 if the user does not specify any ``.o`` files on our command line. Again, this
616 -o <filename> - Specify output filename
671 Sometimes you may want to specify a value to your positional argument that
771 Unix Bourne shell (``/bin/sh``). To run ``/bin/sh``, first you specify options
772 to the shell itself (like ``-x`` which turns on trace output), then you specify
773 the name of the script to run, then you specify arguments to the script. These
776 CommandLine library, we would specify this as:
851 additional argument to our command line argument processor, and we specify where
860 In the above example, we specify "``true``" as the second argument to the
862 the value itself. In addition to this, we specify the `cl::location`_
868 This section describes the basic attributes that you can specify on options.
898 If you specify both **cl::init** and **cl::location** for an option, you
899 must specify **cl::location** first, so that when the command-line parser
918 (option, value, description) triplets that specify the option name, the value
923 #. The **clEnumVal** macro is used as a nice simple way to specify a triplet
928 #. The **clEnumValN** macro is used to specify macro options where the option
966 It is not possible to specify two options from the same category (you'll get a
1071 for the user to specify a value. This can be provided to disallow users from
1075 want them to. As mentioned above, you can specify the `cl::ValueDisallowed`_
1084 The formatting option group is used to specify that the command line option has
1086 As usual, you can only specify one of these arguments at most.
1127 **cl::Grouping** modifiers, but it is possible to specify ambiguous argument
1158 The miscellaneous option modifiers are the only flags where you can specify more
1160 specify boolean properties that modify the option.
1288 template argument is used to specify whether the option should contain the
1354 The `cl::aliasopt`_ attribute should be used to specify which option this is an
