Struct lalrpop::Configuration [−][src]
pub struct Configuration { /* fields omitted */ }
Expand description
Configure various aspects of how LALRPOP works.
Intended for use within a build.rs
script.
To get the default configuration, use Configuration::new
.
Implementations
Creates the default configuration; equivalent to Configuration::default
.
Always use ANSI colors in output, even if output does not appear to be a TTY.
Never use ANSI colors in output, even if output appears to be a TTY.
Use ANSI colors in output if output appears to be a TTY, but not otherwise. This is the default.
Specify a custom directory to search for input files. This
directory is recursively searched for .lalrpop
files to be
considered as input files. This configuration setting also
impacts where output files are placed; paths are made relative
to the input path before being resolved relative to the output
path. By default, the input directory is the current working
directory.
Specify a custom directory to use when writing output files. By default, the output directory is the same as the input directory.
Apply cargo
directory location conventions, by setting the
input directory to src
and the output directory to
$OUT_DIR
.
Write output files in the same directory of the input files.
If this option is enabled, you have to load the parser as a module:
mod parser; // synthesized from parser.lalrpop
This was the default behaviour up to version 0.15.
If true, always convert .lalrpop
files into .rs
files, even if the
.rs
file is newer. Default is false.
If true, print rerun-if-changed
directives to standard output, so that
Cargo will only rerun the build script if any of the processed
.lalrpop
files are changed. This option is independent of
[force_build
], although it would be usual to set [force_build
] and
[emit_rerun_directives
] at the same time.
While many build scripts will want to set this to true
, the default is
false, because emitting any rerun directives to Cargo will cause the
script to only be rerun when Cargo thinks it is needed. This could lead
to hard-to-find bugs if other parts of the build script do not emit
directives correctly, or need to be rerun unconditionally.
If true, emit comments into the generated code. This makes the generated code significantly larger. Default is false.
If false, shrinks the generated code by removing redundant white space. Default is true.
If true, emit report file about generated code.
Minimal logs: only for errors that halt progress.
Informative logs: give some high-level indications of progress (default).
Verbose logs: more than info, but still not overwhelming.
Debug logs: better redirect this to a file. Intended for debugging LALRPOP itself.
pub fn set_features<I>(&mut self, iterable: I) -> &mut Configuration where
I: IntoIterator<Item = String>,
[src]
pub fn set_features<I>(&mut self, iterable: I) -> &mut Configuration where
I: IntoIterator<Item = String>,
[src]Sets the features used during compilation, disables the use of cargo features.
(Default: Loaded from CARGO_FEATURE_{}
environment variables).
Process all files according to the set_in_dir
and
set_out_dir
configuration.
Process all files in the current directory, which – unless you have changed it – is typically the root of the crate being compiled.
Process all .lalrpop
files in path
.
Trait Implementations
Returns the “default value” for a type. Read more
Auto Trait Implementations
impl RefUnwindSafe for Configuration
impl Send for Configuration
impl Sync for Configuration
impl Unpin for Configuration
impl UnwindSafe for Configuration
Blanket Implementations
Mutably borrows from an owned value. Read more