1 .\" Automatically generated by Pod::Man version 1.1
2 .\" Mon Feb 19 19:32:17 2001
5 .\" ======================================================================
6 .de Sh \" Subsection heading
14 .de Sp \" Vertical space (when we can't use .PP)
20 .ie \\n(.$>=3 .ne \\$3
24 .de Vb \" Begin verbatim text
29 .de Ve \" End verbatim text
34 .\" Set up some character translations and predefined strings. \*(-- will
35 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
36 .\" double quote, and \*(R" will give a right double quote. | will give a
37 .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used
38 .\" to do unbreakable dashes and therefore won't be available. \*(C` and
39 .\" \*(C' expand to `' in nroff, nothing in troff, for use with C<>
41 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
45 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
46 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
59 .\" If the F register is turned on, we'll generate index entries on stderr
60 .\" for titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and
61 .\" index entries marked with X<> in POD. Of course, you'll have to process
62 .\" the output yourself in some meaningful fashion.
65 . tm Index:\\$1\t\\n%\t"\\$2"
71 .\" For nroff, turn off justification. Always turn off hyphenation; it
72 .\" makes way too many mistakes in technical documents.
76 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
77 .\" Fear. Run. Save yourself. No user-serviceable parts.
79 . \" fudge factors for nroff and troff
88 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
94 . \" simple accents for nroff and troff
104 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
105 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
106 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
107 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
108 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
109 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
111 . \" troff and (daisy-wheel) nroff accents
112 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
113 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
114 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
115 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
116 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
117 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
118 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
119 .ds ae a\h'-(\w'a'u*4/10)'e
120 .ds Ae A\h'-(\w'A'u*4/10)'E
121 . \" corrections for vroff
122 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
123 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
124 . \" for low resolution devices (crt and lpr)
125 .if \n(.H>23 .if \n(.V>19 \
138 .\" ======================================================================
141 .TH CPP 1 "gcc-3.1" "2001-02-19" "GNU"
144 cpp \- The C Preprocessor
146 .IX Header "SYNOPSIS"
147 cpp [\fB\-P\fR] [\fB\-C\fR] [\fB\-gcc\fR] [\fB\-traditional\fR]
148 [\fB\-undef\fR] [\fB\-trigraphs\fR] [\fB\-pedantic\fR]
149 [\fB\-W\fR\fIwarn\fR...] [\fB\-I\fR\fIdir\fR...]
150 [\fB\-D\fR\fImacro\fR[=\fIdefn\fR]...] [\fB\-U\fR\fImacro\fR]
151 [\fB\-A\fR\fIpredicate\fR(\fIanswer\fR)]
152 [\fB\-M\fR|\fB\-MM\fR][\fB\-MG\fR][\fB\-MF\fR\fIfilename\fR]
153 [\fB\-MP\fR][\fB\-MQ\fR\fItarget\fR...][\fB\-MT\fR\fItarget\fR...]
154 [\fB\-x\fR \fIlanguage\fR] [\fB\-std=\fR\fIstandard\fR]
155 \fIinfile\fR \fIoutfile\fR
157 Only the most useful options are listed here; see below for the remainder.
159 .IX Header "DESCRIPTION"
160 The C preprocessor is a \fImacro processor\fR that is used automatically
161 by the C compiler to transform your program before actual compilation.
162 It is called a macro processor because it allows you to define
163 \&\fImacros\fR, which are brief abbreviations for longer constructs.
165 The C preprocessor is intended only for macro processing of C, \*(C+ and
166 Objective C source files. For macro processing of other files, you are
167 strongly encouraged to use alternatives like M4, which will likely give
168 you better results and avoid many problems. For example, normally the C
169 preprocessor does not preserve arbitrary whitespace verbatim, but
170 instead replaces each sequence with a single space.
172 For use on C-like source files, the C preprocessor provides four
173 separate facilities that you can use as you see fit:
175 Inclusion of header files. These are files of declarations that can be
176 substituted into your program.
178 Macro expansion. You can define \fImacros\fR, which are abbreviations
179 for arbitrary fragments of C code, and then the C preprocessor will
180 replace the macros with their definitions throughout the program.
182 Conditional compilation. Using special preprocessing directives, you
183 can include or exclude parts of the program according to various
186 Line control. If you use a program to combine or rearrange source files
187 into an intermediate file which is then compiled, you can use line
188 control to inform the compiler of where each source line originally came
191 C preprocessors vary in some details. This manual discusses the \s-1GNU\s0 C
192 preprocessor, which provides a small superset of the features of \s-1ISO\s0
195 In its default mode, the \s-1GNU\s0 C preprocessor does not do a few things
196 required by the standard. These are features which are rarely, if ever,
197 used, and may cause surprising changes to the meaning of a program which
198 does not expect them. To get strict \s-1ISO\s0 Standard C, you should use the
199 \&\fB\-std=c89\fR or \fB\-std=c99\fR options, depending on which version
200 of the standard you want. To get all the mandatory diagnostics, you
201 must also use \fB\-pedantic\fR.
204 The C preprocessor expects two file names as arguments, \fIinfile\fR and
205 \&\fIoutfile\fR. The preprocessor reads \fIinfile\fR together with any
206 other files it specifies with \fB#include\fR. All the output generated
207 by the combined input files is written in \fIoutfile\fR.
209 Either \fIinfile\fR or \fIoutfile\fR may be \fB-\fR, which as
210 \&\fIinfile\fR means to read from standard input and as \fIoutfile\fR
211 means to write to standard output. Also, if either file is omitted, it
212 means the same as if \fB-\fR had been specified for that file.
214 Here is a table of command options accepted by the C preprocessor.
215 These options can also be given when compiling a C program; they are
216 passed along automatically to the preprocessor when it is invoked by the
220 Inhibit generation of \fB#\fR\-lines with line-number information in the
221 output from the preprocessor. This might be useful when running the
222 preprocessor on something that is not C code and will be sent to a
223 program which might be confused by the \fB#\fR\-lines.
226 Do not discard comments. All comments are passed through to the output
227 file, except for comments in processed directives, which are deleted
228 along with the directive. Comments appearing in the expansion list of a
229 macro will be preserved, and appear in place wherever the macro is
232 You should be prepared for side effects when using \fB\-C\fR; it causes
233 the preprocessor to treat comments as tokens in their own right. For
234 example, macro redefinitions that were trivial when comments were
235 replaced by a single space might become significant when comments are
236 retained. Also, comments appearing at the start of what would be a
237 directive line have the effect of turning that line into an ordinary
238 source line, since the first token on the line is no longer a \fB#\fR.
239 .Ip "\fB\-traditional\fR" 4
240 .IX Item "-traditional"
241 Try to imitate the behavior of old-fashioned C, as opposed to \s-1ISO\s0 C.
244 Traditional macro expansion pays no attention to single-quote or
245 double-quote characters; macro argument symbols are replaced by the
246 argument values even when they appear within apparent string or
249 Traditionally, it is permissible for a macro expansion to end in the
250 middle of a string or character constant. The constant continues into
251 the text surrounding the macro call.
253 However, traditionally the end of the line terminates a string or
254 character constant, with no error.
256 In traditional C, a comment is equivalent to no text at all. (In \s-1ISO\s0
257 C, a comment counts as whitespace.)
259 Traditional C does not have the concept of a ``preprocessing number''.
260 It considers \fB1.0e+4\fR to be three tokens: \fB1.0e\fR, \fB+\fR,
263 A macro is not suppressed within its own definition, in traditional C.
264 Thus, any macro that is used recursively inevitably causes an error.
266 The character \fB#\fR has no special meaning within a macro definition
269 In traditional C, the text at the end of a macro expansion can run
270 together with the text after the macro call, to produce a single token.
271 (This is impossible in \s-1ISO\s0 C.)
273 None of the \s-1GNU\s0 extensions to the preprocessor are available in
274 \&\fB\-traditional\fR mode.
278 Use the \fB\-traditional\fR option when preprocessing Fortran code, so
279 that single-quotes and double-quotes within Fortran comment lines (which
280 are generally not recognized as such by the preprocessor) do not cause
281 diagnostics about unterminated character or string constants.
283 However, this option does not prevent diagnostics about unterminated
284 comments when a C-style comment appears to start, but not end, within
285 Fortran-style commentary.
287 So, the following Fortran comment lines are accepted with
288 \&\fB\-traditional\fR:
291 \& C This isn't an unterminated character constant
292 \& C Neither is "20000000000, an octal constant
293 \& C in some dialects of Fortran
295 However, this type of comment line will likely produce a diagnostic, or
296 at least unexpected output from the preprocessor, due to the
297 unterminated comment:
300 \& C Some Fortran compilers accept /* as starting
301 \& C an inline comment.
303 Note that \f(CW\*(C`g77\*(C'\fR automatically supplies the \fB\-traditional\fR
304 option when it invokes the preprocessor. However, a future version of
305 \&\f(CW\*(C`g77\*(C'\fR might use a different, more-Fortran-aware preprocessor in
306 place of \f(CW\*(C`cpp\*(C'\fR.
308 .Ip "\fB\-trigraphs\fR" 4
309 .IX Item "-trigraphs"
310 Process \s-1ISO\s0 standard trigraph sequences. These are three-character
311 sequences, all starting with \fB??\fR, that are defined by \s-1ISO\s0 C to
312 stand for single characters. For example, \fB??/\fR stands for
313 \&\fB\e\fR, so \fB'??/n'\fR is a character constant for a newline. By
314 default, \s-1GCC\s0 ignores trigraphs, but in standard-conforming modes it
315 converts them. See the \fB\-std\fR option.
317 The nine trigraph sequences are
349 Trigraph support is not popular, so many compilers do not implement it
350 properly. Portable code should not rely on trigraphs being either
351 converted or ignored.
353 .Ip "\fB\-pedantic\fR" 4
355 Issue warnings required by the \s-1ISO\s0 C standard in certain cases such
356 as when text other than a comment follows \fB#else\fR or \fB#endif\fR.
357 .Ip "\fB\-pedantic-errors\fR" 4
358 .IX Item "-pedantic-errors"
359 Like \fB\-pedantic\fR, except that errors are produced rather than
361 .Ip "\fB\-Wcomment\fR" 4
364 .Ip "\fB\-Wcomments\fR" 4
365 .IX Item "-Wcomments"
367 (Both forms have the same effect).
368 Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR
369 comment, or whenever a backslash-newline appears in a \fB//\fR comment.
370 .Ip "\fB\-Wtrigraphs\fR" 4
371 .IX Item "-Wtrigraphs"
372 Warn if any trigraphs are encountered. This option used to take effect
373 only if \fB\-trigraphs\fR was also specified, but now works
374 independently. Warnings are not given for trigraphs within comments, as
375 we feel this is obnoxious.
376 .Ip "\fB\-Wwhite-space\fR" 4
377 .IX Item "-Wwhite-space"
378 Warn about possible white space confusion, e.g. white space between a
379 backslash and a newline.
382 Requests \fB\-Wcomment\fR, \fB\-Wtrigraphs\fR, and \fB\-Wwhite-space\fR
383 (but not \fB\-Wtraditional\fR or \fB\-Wundef\fR).
384 .Ip "\fB\-Wtraditional\fR" 4
385 .IX Item "-Wtraditional"
386 Warn about certain constructs that behave differently in traditional and
390 Macro parameters that appear within string literals in the macro body.
391 In traditional C macro replacement takes place within string literals,
392 but does not in \s-1ISO\s0 C.
394 In traditional C, some preprocessor directives did not exist.
395 Traditional preprocessors would only consider a line to be a directive
396 if the \fB#\fR appeared in column 1 on the line. Therefore
397 \&\fB\-Wtraditional\fR warns about directives that traditional C
398 understands but would ignore because the \fB#\fR does not appear as the
399 first character on the line. It also suggests you hide directives like
400 \&\fB#pragma\fR not understood by traditional C by indenting them. Some
401 traditional implementations would not recognise \fB#elif\fR, so it
402 suggests avoiding it altogether.
404 A function-like macro that appears without arguments.
406 The unary plus operator.
408 The `U' integer constant suffix. (Traditonal C does support the `L'
409 suffix on integer constants.) Note, these suffixes appear in macros
410 defined in the system headers of most modern systems, e.g. the _MIN/_MAX
411 macros in limits.h. Use of these macros can lead to spurious warnings
412 as they do not necessarily reflect whether the code in question is any
413 less portable to traditional C given that suitable backup definitions
418 .Ip "\fB\-Wundef\fR" 4
420 Warn if an undefined identifier is evaluated in an \fB#if\fR directive.
421 .Ip "\fB\-I\fR \fIdirectory\fR" 4
422 .IX Item "-I directory"
423 Add the directory \fIdirectory\fR to the head of the list of
424 directories to be searched for header files.
425 This can be used to override a system header file, substituting your
426 own version, since these directories are searched before the system
427 header file directories. If you use more than one \fB\-I\fR option,
428 the directories are scanned in left-to-right order; the standard
429 system directories come after.
432 Any directories specified with \fB\-I\fR options before the \fB\-I-\fR
433 option are searched only for the case of \fB#include "\fR\fIfile\fR\fB"\fR;
434 they are not searched for \fB#include <\fR\fIfile\fR\fB>\fR.
436 If additional directories are specified with \fB\-I\fR options after
437 the \fB\-I-\fR, these directories are searched for all \fB#include\fR
440 In addition, the \fB\-I-\fR option inhibits the use of the current
441 directory as the first search directory for \fB#include "\fR\fIfile\fR\fB"\fR.
442 Therefore, the current directory is searched only if it is requested
443 explicitly with \fB\-I.\fR. Specifying both \fB\-I-\fR and \fB\-I.\fR
444 allows you to control precisely which directories are searched before
445 the current one and which are searched after.
446 .Ip "\fB\-nostdinc\fR" 4
448 Do not search the standard system directories for header files.
449 Only the directories you have specified with \fB\-I\fR options
450 (and the current directory, if appropriate) are searched.
452 By using both \fB\-nostdinc\fR and \fB\-I-\fR, you can limit the include-file
453 search path to only those directories you specify explicitly.
454 .Ip "\fB\-nostdinc++\fR" 4
455 .IX Item "-nostdinc++"
456 Do not search for header files in the \*(C+\-specific standard directories,
457 but do still search the other standard directories. (This option is
458 used when building the \*(C+ library.)
459 .Ip "\fB\-remap\fR" 4
461 When searching for a header file in a directory, remap file names if a
462 file named \fIheader.gcc\fR exists in that directory. This can be used
463 to work around limitations of file systems with file name restrictions.
464 The \fIheader.gcc\fR file should contain a series of lines with two
465 tokens on each line: the first token is the name to map, and the second
466 token is the actual name to use.
467 .Ip "\fB\-D\fR \fIname\fR" 4
469 Predefine \fIname\fR as a macro, with definition \fB1\fR.
470 .Ip "\fB\-D\fR \fIname\fR\fB=\fR\fIdefinition\fR" 4
471 .IX Item "-D name=definition"
472 Predefine \fIname\fR as a macro, with definition \fIdefinition\fR.
473 There are no restrictions on the contents of \fIdefinition\fR, but if
474 you are invoking the preprocessor from a shell or shell-like program you
475 may need to use the shell's quoting syntax to protect characters such as
476 spaces that have a meaning in the shell syntax. If you use more than
477 one \fB\-D\fR for the same \fIname\fR, the rightmost definition takes
480 Any \fB\-D\fR and \fB\-U\fR options on the command line are processed in
481 order, and always before \fB\-imacros\fR \fIfile\fR, regardless of the
482 order in which they are written.
483 .Ip "\fB\-U\fR \fIname\fR" 4
485 Do not predefine \fIname\fR.
487 Any \fB\-D\fR and \fB\-U\fR options on the command line are processed in
488 order, and always before \fB\-imacros\fR \fIfile\fR, regardless of the
489 order in which they are written.
490 .Ip "\fB\-undef\fR" 4
492 Do not predefine any nonstandard macros.
495 Define the macros \fI_\|_GNUC_\|_\fR, \fI_\|_GNUC_MINOR_\|_\fR and
496 \&\fI_\|_GNUC_PATCHLEVEL_\|_\fR. These are defined automatically when you use
497 \&\fBgcc \-E\fR; you can turn them off in that case with \fB\-no-gcc\fR.
498 .Ip "\fB\-A\fR \fIpredicate\fR\fB=\fR\fIanswer\fR" 4
499 .IX Item "-A predicate=answer"
500 Make an assertion with the predicate \fIpredicate\fR and answer
501 \&\fIanswer\fR. This form is preferred to the older form \fB\-A\fR
502 \&\fIpredicate\fR\fB(\fR\fIanswer\fR\fB)\fR, which is still supported, because
503 it does not use shell special characters.
504 .Ip "\fB\-A -\fR\fIpredicate\fR\fB=\fR\fIanswer\fR" 4
505 .IX Item "-A -predicate=answer"
506 Disable an assertion with the predicate \fIpredicate\fR and answer
507 \&\fIanswer\fR. Specifying no predicate, by \fB\-A-\fR or \fB\-A -\fR,
508 disables all predefined assertions and all assertions preceding it on
509 the command line; and also undefines all predefined macros and all
510 macros preceding it on the command line.
513 Instead of outputting the result of preprocessing, output a list of
514 \&\fB#define\fR directives for all the macros defined during the
515 execution of the preprocessor, including predefined macros. This gives
516 you a way of finding out what is predefined in your version of the
517 preprocessor; assuming you have no file \fBfoo.h\fR, the command
520 \& touch foo.h; cpp -dM foo.h
522 will show the values of any predefined macros.
525 Like \fB\-dM\fR except in two respects: it does \fInot\fR include the
526 predefined macros, and it outputs \fIboth\fR the \fB#define\fR
527 directives and the result of preprocessing. Both kinds of output go to
528 the standard output file.
531 Like \fB\-dD\fR, but emit only the macro names, not their expansions.
534 Output \fB#include\fR directives in addition to the result of
538 Instead of outputting the result of preprocessing, output a rule
539 suitable for \f(CW\*(C`make\*(C'\fR describing the dependencies of the main source
540 file. The preprocessor outputs one \f(CW\*(C`make\*(C'\fR rule containing the
541 object file name for that source file, a colon, and the names of all the
542 included files, including those coming from \fB\-include\fR or
543 \&\fB\-imacros\fR command line options. Unless specified explicitly (with
544 \&\fB\-MT\fR or \fB\-MQ\fR), the object file name consists of the basename
545 of the source file with any suffix replaced with object file suffix.
546 If there are many included files
547 then the rule is split into several lines using \fB\e\fR\-newline.
550 Like \fB\-M\fR, but mention only the files included with \fB#include
551 "\fR\fIfile\fR\fB"\fR or with \fB\-include\fR or \fB\-imacros\fR command line
552 options. System header files included with \fB#include <\fR\fIfile\fR\fB>\fR
554 .Ip "\fB\-MF\fR \fIfile\fR" 4
556 When used with \fB\-M\fR or \fB\-MM\fR, specifies a file to write the
557 dependencies to. This allows the preprocessor to write the preprocessed
558 file to stdout normally. If no \fB\-MF\fR switch is given, \s-1CPP\s0 sends
559 the rules to stdout and suppresses normal preprocessed output.
562 When used with \fB\-M\fR or \fB\-MM\fR, \fB\-MG\fR says to treat missing
563 header files as generated files and assume they live in the same
564 directory as the source file. It suppresses preprocessed output, as a
565 missing header file is ordinarily an error.
567 This feature is used in automatic updating of makefiles.
570 This option instructs \s-1CPP\s0 to add a phony target for each dependency
571 other than the main file, causing each to depend on nothing. These
572 dummy rules work around errors \f(CW\*(C`make\*(C'\fR gives if you remove header
573 files without updating the \f(CW\*(C`Makefile\*(C'\fR to match.
575 This is typical output:\-
578 \& /tmp/test.o: /tmp/test.c /tmp/test.h
583 .Ip "\fB\-MQ\fR \fItarget\fR" 4
584 .IX Item "-MQ target"
586 .Ip "\fB\-MT\fR \fItarget\fR" 4
587 .IX Item "-MT target"
589 By default \s-1CPP\s0 uses the main file name, including any path, and appends
590 the object suffix, normally ``.o'', to it to obtain the name of the
591 target for dependency generation. With \fB\-MT\fR you can specify a
592 target yourself, overriding the default one.
594 If you want multiple targets, you can specify them as a single argument
595 to \fB\-MT\fR, or use multiple \fB\-MT\fR options.
597 The targets you specify are output in the order they appear on the
598 command line. \fB\-MQ\fR is identical to \fB\-MT\fR, except that the
599 target name is quoted for Make, but with \fB\-MT\fR it isn't. For
600 example, \-MT '$(objpfx)foo.o' gives
603 \& $(objpfx)foo.o: /tmp/foo.c
605 but \-MQ '$(objpfx)foo.o' gives
608 \& $$(objpfx)foo.o: /tmp/foo.c
610 The default target is automatically quoted, as if it were given with
614 Print the name of each header file used, in addition to other normal
616 .Ip "\fB\-imacros\fR \fIfile\fR" 4
617 .IX Item "-imacros file"
618 Process \fIfile\fR as input, discarding the resulting output, before
619 processing the regular input file. Because the output generated from
620 \&\fIfile\fR is discarded, the only effect of \fB\-imacros\fR \fIfile\fR
621 is to make the macros defined in \fIfile\fR available for use in the
623 .Ip "\fB\-include\fR \fIfile\fR" 4
624 .IX Item "-include file"
625 Process \fIfile\fR as input, and include all the resulting output,
626 before processing the regular input file.
627 .Ip "\fB\-idirafter\fR \fIdir\fR" 4
628 .IX Item "-idirafter dir"
629 Add the directory \fIdir\fR to the second include path. The directories
630 on the second include path are searched when a header file is not found
631 in any of the directories in the main include path (the one that
632 \&\fB\-I\fR adds to).
633 .Ip "\fB\-iprefix\fR \fIprefix\fR" 4
634 .IX Item "-iprefix prefix"
635 Specify \fIprefix\fR as the prefix for subsequent \fB\-iwithprefix\fR
636 options. If the prefix represents a directory, you should include the
638 .Ip "\fB\-iwithprefix\fR \fIdir\fR" 4
639 .IX Item "-iwithprefix dir"
640 Add a directory to the second include path. The directory's name is
641 made by concatenating \fIprefix\fR and \fIdir\fR, where \fIprefix\fR was
642 specified previously with \fB\-iprefix\fR.
643 .Ip "\fB\-isystem\fR \fIdir\fR" 4
644 .IX Item "-isystem dir"
645 Add a directory to the beginning of the second include path, marking it
646 as a system directory, so that it gets the same special treatment as
647 is applied to the standard system directories.
651 .Ip "\fB\-x c++\fR" 4
653 .Ip "\fB\-x objective-c\fR" 4
654 .IX Item "-x objective-c"
655 .Ip "\fB\-x assembler-with-cpp\fR" 4
656 .IX Item "-x assembler-with-cpp"
658 Specify the source language: C, \*(C+, Objective-C, or assembly. This has
659 nothing to do with standards conformance or extensions; it merely
660 selects which base syntax to expect. If you give none of these options,
661 cpp will deduce the language from the extension of the source file:
662 \&\fB.c\fR, \fB.cc\fR, \fB.m\fR, or \fB.S\fR. Some other common
663 extensions for \*(C+ and assembly are also recognized. If cpp does not
664 recognize the extension, it will treat the file as C; this is the most
667 \&\fBNote:\fR Previous versions of cpp accepted a \fB\-lang\fR option
668 which selected both the language and the standards conformance level.
669 This option has been removed, because it conflicts with the \fB\-l\fR
671 .Ip "\fB\-std=\fR\fIstandard\fR" 4
672 .IX Item "-std=standard"
677 Specify the standard to which the code should conform. Currently cpp
678 only knows about the standards for C; other language standards will be
684 .if n .Ip "\f(CW""iso9899:1990""\fR" 4
685 .el .Ip "\f(CWiso9899:1990\fR" 4
686 .IX Item "iso9899:1990"
688 .if n .Ip "\f(CW""c89""\fR" 4
689 .el .Ip "\f(CWc89\fR" 4
692 The \s-1ISO\s0 C standard from 1990. \fBc89\fR is the customary shorthand for
693 this version of the standard.
695 The \fB\-ansi\fR option is equivalent to \fB\-std=c89\fR.
696 .if n .Ip "\f(CW""iso9899:199409""\fR" 4
697 .el .Ip "\f(CWiso9899:199409\fR" 4
698 .IX Item "iso9899:199409"
699 The 1990 C standard, as amended in 1994.
700 .if n .Ip "\f(CW""iso9899:1999""\fR" 4
701 .el .Ip "\f(CWiso9899:1999\fR" 4
702 .IX Item "iso9899:1999"
704 .if n .Ip "\f(CW""c99""\fR" 4
705 .el .Ip "\f(CWc99\fR" 4
707 .if n .Ip "\f(CW""iso9899:199x""\fR" 4
708 .el .Ip "\f(CWiso9899:199x\fR" 4
709 .IX Item "iso9899:199x"
710 .if n .Ip "\f(CW""c9x""\fR" 4
711 .el .Ip "\f(CWc9x\fR" 4
714 The revised \s-1ISO\s0 C standard, published in December 1999. Before
715 publication, this was known as C9X.
716 .if n .Ip "\f(CW""gnu89""\fR" 4
717 .el .Ip "\f(CWgnu89\fR" 4
719 The 1990 C standard plus \s-1GNU\s0 extensions. This is the default.
720 .if n .Ip "\f(CW""gnu99""\fR" 4
721 .el .Ip "\f(CWgnu99\fR" 4
724 .if n .Ip "\f(CW""gnu9x""\fR" 4
725 .el .Ip "\f(CWgnu9x\fR" 4
728 The 1999 C standard plus \s-1GNU\s0 extensions.
732 .Ip "\fB\-ftabstop=NUMBER\fR" 4
733 .IX Item "-ftabstop=NUMBER"
734 Set the distance between tab stops. This helps the preprocessor
735 report correct column numbers in warnings or errors, even if tabs appear
736 on the line. Values less than 1 or greater than 100 are ignored. The
740 Forbid the use of \fB$\fR in identifiers. The C standard allows
741 implementations to define extra characters that can appear in
742 identifiers. By default the \s-1GNU\s0 C preprocessor permits \fB$\fR, a
745 .IX Header "SEE ALSO"
746 \&\fIgcc\fR\|(1), \fIas\fR\|(1), \fIld\fR\|(1), and the Info entries for \fIcpp\fR, \fIgcc\fR, and
749 .IX Header "COPYRIGHT"
750 Copyright (c) 1987, 1989, 1991, 1992, 1993, 1994, 1995, 1996,
751 1997, 1998, 1999, 2000, 2001
752 Free Software Foundation, Inc.
754 Permission is granted to make and distribute verbatim copies of
755 this manual provided the copyright notice and this permission notice
756 are preserved on all copies.
758 Permission is granted to copy and distribute modified versions of this
759 manual under the conditions for verbatim copying, provided also that
760 the entire resulting derived work is distributed under the terms of a
761 permission notice identical to this one.
763 Permission is granted to copy and distribute translations of this manual
764 into another language, under the above conditions for modified versions.
OSDN Git Service
