diff options
Diffstat (limited to 'doc/generated/variables.gen')
| -rw-r--r-- | doc/generated/variables.gen | 118 |
1 files changed, 111 insertions, 7 deletions
diff --git a/doc/generated/variables.gen b/doc/generated/variables.gen index 533ea2293..fdfa9bc9c 100644 --- a/doc/generated/variables.gen +++ b/doc/generated/variables.gen @@ -3926,6 +3926,31 @@ The lexical analyzer generator. </para> </listitem> </varlistentry> + <varlistentry id="cv-LEX_HEADER_FILE"> + <term> + <envar>LEX_HEADER_FILE</envar> + </term> + <listitem><para> +If supplied, generate a C header file with the name taken from this variable. +Will be emitted as a <option>--header-file=</option> +command-line option. Use this in preference to including +<option>--header-file=</option> in &cv-link-LEXFLAGS; directly. +</para> +</listitem> + </varlistentry> + <varlistentry id="cv-LEX_TABLES_FILE"> + <term> + <envar>LEX_TABLES_FILE</envar> + </term> + <listitem><para> +If supplied, write the lex tables to a file with the name +taken from this variable. +Will be emitted as a <option>--tables-file=</option> +command-line option. Use this in preference to including +<option>--tables-file=</option> in &cv-link-LEXFLAGS; directly. +</para> +</listitem> + </varlistentry> <varlistentry id="cv-LEXCOM"> <term> <envar>LEXCOM</envar> @@ -3947,7 +3972,7 @@ If this is not set, then &cv-link-LEXCOM; (the command line) is displayed. </para> <example_commands> -env = Environment(LEXCOMSTR = "Lex'ing $TARGET from $SOURCES") +env = Environment(LEXCOMSTR="Lex'ing $TARGET from $SOURCES") </example_commands> </listitem> </varlistentry> @@ -3957,6 +3982,20 @@ env = Environment(LEXCOMSTR = "Lex'ing $TARGET from $SOURCES") </term> <listitem><para> General options passed to the lexical analyzer generator. +In addition to passing the value on during invocation, +the &t-link-lex; tool also examines this &consvar; for options +which cause additional output files to be generated, +and adds those to the target list. +Recognized for this purpose are GNU &flex; options +<option>--header-file=</option> and +<option>--tables-file=</option>; +the output file is named by the option argument. +</para> +<para> +Note that files specified by <option>--header-file=</option> and +<option>--tables-file=</option> may not be properly handled +by &SCons; in all situations. Consider using +&cv-link-LEX_HEADER_FILE; and &cv-link-LEX_TABLES_FILE; instead. </para> </listitem> </varlistentry> @@ -10032,6 +10071,31 @@ The parser generator. </para> </listitem> </varlistentry> + <varlistentry id="cv-YACC_GRAPH_FILE"> + <term> + <envar>YACC_GRAPH_FILE</envar> + </term> + <listitem><para> +If supplied, write a graph of the automaton to a file with the name +taken from this variable. +Will be emitted as a <option>--graph=</option> +command-line option. Use this in preference to including +<option>--graph=</option> in &cv-link-YACCFLAGS; directly. +</para> +</listitem> + </varlistentry> + <varlistentry id="cv-YACC_HEADER_FILE"> + <term> + <envar>YACC_HEADER_FILE</envar> + </term> + <listitem><para> +If supplied, generate a header file with the name taken from this variable. +Will be emitted as a <option>--header=</option> +command-line option. Use this in preference to including +<option>--header=</option> in &cv-link-YACCFLAGS; directly. +</para> +</listitem> + </varlistentry> <varlistentry id="cv-YACCCOM"> <term> <envar>YACCCOM</envar> @@ -10053,7 +10117,7 @@ If this is not set, then &cv-link-YACCCOM; (the command line) is displayed. </para> <example_commands> -env = Environment(YACCCOMSTR = "Yacc'ing $TARGET from $SOURCES") +env = Environment(YACCCOMSTR="Yacc'ing $TARGET from $SOURCES") </example_commands> </listitem> </varlistentry> @@ -10063,11 +10127,51 @@ env = Environment(YACCCOMSTR = "Yacc'ing $TARGET from $SOURCES") </term> <listitem><para> General options passed to the parser generator. -If &cv-link-YACCFLAGS; contains a <option>-d</option> option, -SCons assumes that the call will also create a .h file -(if the yacc source file ends in a .y suffix) -or a .hpp file -(if the yacc source file ends in a .yy suffix) +In addition to passing the value on during invocation, +the &t-link-yacc; tool also examines this &consvar; for options +which cause additional output files to be generated, +and adds those to the target list. +</para> + +<para> +If a <option>-d</option> option is present, +&scons; assumes that the call will also create a header file +with the suffix defined by &cv-link-YACCHFILESUFFIX; +if the yacc source file ends in a <filename>.y</filename> suffix, +or a file with the suffix defined by &cv-link-YACCHXXFILESUFFIX; +if the yacc source file ends in a <filename>.yy</filename> suffix. +</para> + +<para> +If a <option>-g</option> option is present, +&scons; assumes that the call will also create a graph file +with the suffix defined by &cv-link-YACCVCGFILESUFFIX;. +</para> + +<para> +If a <option>-v</option> option is present, +&scons; assumes that the call will also create an output debug file +with the suffix <filename>.output</filename>. +</para> + +<para> +Also recognized are GNU &bison; options +<option>--header=</option> and its deprecated synonym +<option>--defines=</option>, +which is similar to +<option>-d</option> +but the output filename is named by the option argument; +and <option>--graph=</option>, +which is similar to +<option>-g</option> +but the output filename is named by the option argument. +</para> + +<para> +Note that files specified by <option>--header=</option> and +<option>--graph=</option> may not be properly handled +by &SCons; in all situations. Consider using +&cv-link-YACC_HEADER_FILE; and &cv-link-YACC_GRAPH_FILE; instead. </para> </listitem> </varlistentry> |