Lines Matching full:specify
39 #. Globally accessible: Libraries can specify command line arguments that are
56 Simply specify the parser that you want to use with the command line option
105 we would like to support the Unix-standard '``-o <filename>``' option to specify
114 cl::opt<string> OutputFilename("o", cl::desc("Specify output filename"), cl::value_desc("filename"));
117 result of the "``o``" argument (first parameter). We specify that this is a
122 The second and third parameters (which are optional) are used to specify what to
132 -o <filename> - Specify output filename
166 as the input filename. Here we use the `cl::init`_ option to specify an initial
168 (if you do not specify a `cl::init`_ modifier for an option, then the default
171 always specify an input filename, we would add the `cl::Required`_ flag, and we
198 -o <filename> - Specify output filename
313 ... which is much nicer! The "`cl::alias`_" can be used to specify an
325 The answer is that it uses a table-driven generic parser (unless you specify
335 #. A user could specify more than one of the options at a time, for example,
369 the user can only specify one of the options, and it ensure that only valid enum
386 -o <filename> - Specify output filename
412 specify the name that the flag should get. In general a direct mapping is nice,
420 style in our compiler to specify different debug levels that can be used.
425 optimization level flags, but we also specify an option name. For this case,
463 -o <filename> - Specify output filename
532 if the user does not specify any ``.o`` files on our command line. Again, this
619 -o <filename> - Specify output filename
723 Sometimes you may want to specify a value to your positional argument that
823 Unix Bourne shell (``/bin/sh``). To run ``/bin/sh``, first you specify options
824 to the shell itself (like ``-x`` which turns on trace output), then you specify
825 specify arguments to the script. These
828 CommandLine library, we would specify this as:
903 additional argument to our command line argument processor, and we specify where
912 In the above example, we specify "``true``" as the second argument to the
914 the value itself. In addition to this, we specify the `cl::location`_
920 This section describes the basic attributes that you can specify on options.
951 If you specify both **cl::init** and **cl::location** for an option, you
952 must specify **cl::location** first, so that when the command-line parser
971 (option, value, description) triplets that specify the option name, the value
976 #. The **clEnumVal** macro is used as a nice simple way to specify a triplet
981 #. The **clEnumValN** macro is used to specify macro options where the option
1024 It is not possible to specify two options from the same category (you'll get a
1129 for the user to specify a value. This can be provided to disallow users from
1133 want them to. As mentioned above, you can specify the `cl::ValueDisallowed`_
1142 The formatting option group is used to specify that the command line option has
1144 As usual, you can only specify one of these arguments at most.
1185 **cl::Grouping** modifiers, but it is possible to specify ambiguous argument
1216 The miscellaneous option modifiers are the only flags where you can specify more
1218 specify boolean properties that modify the option.
1397 template argument is used to specify whether the option should contain the
1463 The `cl::aliasopt`_ attribute should be used to specify which option this is an
