1 # Sample TOML configuration file for building Rust.
3 # To configure rustbuild, copy this file to the directory from which you will be
4 # running the build, and name it config.toml.
6 # All options are commented out by default in this file, and they're commented
7 # out with their default values. The build system by default looks for
8 # `config.toml` in the current directory of a build for build configuration, but
9 # a custom configuration file can also be specified with `--config` to the build
12 # Keeps track of the last version of `x.py` used.
13 # If it does not match the version that is currently running,
14 # `x.py` will prompt you to update it and read the changelog.
15 # See `src/bootstrap/CHANGELOG.md` for more information.
18 # =============================================================================
20 # =============================================================================
22 # Use different pre-set defaults than the global defaults.
24 # See `src/bootstrap/defaults` for more information.
25 # Note that this has no default value (x.py uses the defaults in `config.toml.example`).
28 # =============================================================================
29 # Tweaking how LLVM is compiled
30 # =============================================================================
33 # Whether to use Rust CI built LLVM instead of locally building it.
35 # Unless you're developing for a target where Rust CI doesn't build a compiler
36 # toolchain or changing LLVM locally, you probably want to set this to true.
38 # All tier 1 targets are currently supported; set this to `"if-available"` if
39 # you are not sure whether you're on a tier 1 target.
41 # We also currently only support this when building LLVM for the build triple.
43 # Note that many of the LLVM options are not currently supported for
44 # downloading. Currently only the "assertions" option can be toggled.
46 # Defaults to "if-available" when `channel = "dev"` and "false" otherwise.
47 #download-ci-llvm = "if-available"
49 # Indicates whether LLVM rebuild should be skipped when running bootstrap. If
50 # this is `false` then the compiler's LLVM will be rebuilt whenever the built
51 # version doesn't have the correct hash. If it is `true` then LLVM will never
52 # be rebuilt. The default value is `false`.
55 # Indicates whether the LLVM build is a Release or Debug build
58 # Indicates whether LLVM should be built with ThinLTO. Note that this will
59 # only succeed if you use clang, lld, llvm-ar, and llvm-ranlib in your C/C++
60 # toolchain (see the `cc`, `cxx`, `linker`, `ar`, and `ranlib` options below).
61 # More info at: https://clang.llvm.org/docs/ThinLTO.html#clang-bootstrap
64 # Indicates whether an LLVM Release build should include debug info
65 #release-debuginfo = false
67 # Indicates whether the LLVM assertions are enabled or not
70 # Indicates whether the LLVM testsuite is enabled in the build or not. Does
71 # not execute the tests as part of the build as part of x.py build et al,
72 # just makes it possible to do `ninja check-llvm` in the staged LLVM build
73 # directory when doing LLVM development as part of Rust development.
76 # Indicates whether the LLVM plugin is enabled or not
79 # Indicates whether ccache is used when building LLVM
81 # or alternatively ...
82 #ccache = "/path/to/ccache"
84 # If an external LLVM root is specified, we automatically check the version by
85 # default to make sure it's within the range that we're expecting, but setting
86 # this flag will indicate that this version check should not be done.
89 # When true, link libstdc++ statically into the rustc_llvm.
90 # This is useful if you don't want to use the dynamic version of that
91 # library provided by LLVM.
92 #static-libstdcpp = false
94 # Whether to use Ninja to build LLVM. This runs much faster than make.
97 # LLVM targets to build support for.
98 # Note: this is NOT related to Rust compilation targets. However, as Rust is
99 # dependent on LLVM for code generation, turning targets off here WILL lead to
100 # the resulting rustc being unable to compile for the disabled architectures.
101 # Also worth pointing out is that, in case support for new targets are added to
102 # LLVM, enabling them here doesn't mean Rust is automatically gaining said
103 # support. You'll need to write a target specification at least, and most
104 # likely, teach rustc about the C ABI of the target. Get in touch with the
105 # Rust team and file an issue if you need assistance in porting!
106 #targets = "AArch64;ARM;BPF;Hexagon;MSP430;Mips;NVPTX;PowerPC;RISCV;Sparc;SystemZ;WebAssembly;X86"
108 # LLVM experimental targets to build support for. These targets are specified in
109 # the same format as above, but since these targets are experimental, they are
110 # not built by default and the experimental Rust compilation targets that depend
111 # on them will not work unless the user opts in to building them.
112 #experimental-targets = "AVR;M68k"
114 # Cap the number of parallel linker invocations when compiling LLVM.
115 # This can be useful when building LLVM with debug info, which significantly
116 # increases the size of binaries and consequently the memory required by
117 # each linker process.
118 # If absent or 0, linker invocations are treated like any other job and
119 # controlled by rustbuild's -j parameter.
122 # When invoking `llvm-config` this configures whether the `--shared` argument is
123 # passed to prefer linking to shared libraries.
124 # NOTE: `thin-lto = true` requires this to be `true` and will give an error otherwise.
127 # When building llvm, this configures what is being appended to the version.
128 # The default is "-rust-$version-$channel", except for dev channel where rustc
129 # version number is omitted. To use LLVM version as is, provide an empty string.
130 #version-suffix = "-rust-dev"
132 # On MSVC you can compile LLVM with clang-cl, but the test suite doesn't pass
133 # with clang-cl, so this is special in that it only compiles LLVM with clang-cl.
134 # Note that this takes a /path/to/clang-cl, not a boolean.
137 # Pass extra compiler and linker flags to the LLVM CMake build.
142 # Use libc++ when building LLVM instead of libstdc++. This is the default on
143 # platforms already use libc++ as the default C++ library, but this option
144 # allows you to use libc++ even on platforms when it's not. You need to ensure
145 # that your host compiler ships with libc++.
148 # The value specified here will be passed as `-DLLVM_USE_LINKER` to CMake.
149 #use-linker = <none> (path)
151 # Whether or not to specify `-DLLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN=YES`
152 #allow-old-toolchain = false
154 # Whether to include the Polly optimizer.
157 # Whether to build the clang compiler.
160 # Custom CMake defines to set when building LLVM.
163 # =============================================================================
164 # General build configuration options
165 # =============================================================================
167 # The default stage to use for the `check` subcommand
170 # The default stage to use for the `doc` subcommand
173 # The default stage to use for the `build` subcommand
176 # The default stage to use for the `test` subcommand
179 # The default stage to use for the `dist` subcommand
182 # The default stage to use for the `install` subcommand
185 # The default stage to use for the `bench` subcommand
188 # Build triple for the original snapshot compiler. This must be a compiler that
189 # nightlies are already produced for. The current platform must be able to run
190 # binaries of this build triple and the nightly will be used to bootstrap the
193 # Defaults to platform where `x.py` is run.
194 #build = "x86_64-unknown-linux-gnu" (as an example)
196 # Which triples to produce a compiler toolchain for. Each of these triples will
197 # be bootstrapped from the build triple themselves.
199 # Defaults to just the build triple.
200 #host = ["x86_64-unknown-linux-gnu"] (as an example)
202 # Which triples to build libraries (core/alloc/std/test/proc_macro) for. Each of
203 # these triples will be bootstrapped from the build triple themselves.
205 # Defaults to `host`. If you set this explicitly, you likely want to add all
206 # host triples to this list as well in order for those host toolchains to be
207 # able to compile programs for their native target.
208 #target = ["x86_64-unknown-linux-gnu"] (as an example)
210 # Use this directory to store build artifacts.
211 # You can use "$ROOT" to indicate the root of the git repository.
214 # Instead of downloading the src/stage0.json version of Cargo specified, use
215 # this Cargo binary instead to build all Rust code
216 #cargo = "/path/to/cargo"
218 # Instead of downloading the src/stage0.json version of the compiler
219 # specified, use this rustc binary instead as the stage0 snapshot compiler.
220 #rustc = "/path/to/rustc"
222 # Instead of download the src/stage0.json version of rustfmt specified,
223 # use this rustfmt binary instead as the stage0 snapshot rustfmt.
224 #rustfmt = "/path/to/rustfmt"
226 # Flag to specify whether any documentation is built. If false, rustdoc and
227 # friends will still be compiled but they will not be used to generate any
231 # Flag to specify whether CSS, JavaScript, and HTML are minified when
232 # docs are generated. JSON is always minified, because it's enormous,
233 # and generated in already-minified form from the beginning.
234 #docs-minification = true
236 # Flag to specify whether private items should be included in the library docs.
237 #library-docs-private-items = false
239 # Indicate whether the compiler should be documented in addition to the standard
240 # library and facade crates.
241 #compiler-docs = false
243 # Indicate whether git submodules are managed and updated automatically.
246 # The path to (or name of) the GDB executable to use. This is only used for
247 # executing the debuginfo test suite.
250 # The node.js executable to use. Note that this is only used for the emscripten
251 # target when running tests, otherwise this can be omitted.
254 # Python interpreter to use for various tasks throughout the build, notably
255 # rustdoc tests, the lldb python interpreter, and some dist bits and pieces.
257 # Defaults to the Python interpreter used to execute x.py
260 # The path to the REUSE executable to use. Note that REUSE is not required in
261 # most cases, as our tooling relies on a cached (and shrinked) copy of the
262 # REUSE output present in the git repository and in our source tarballs.
264 # REUSE is only needed if your changes caused the overral licensing of the
265 # repository to change, and the cached copy has to be regenerated.
267 # Defaults to the "reuse" command in the system path.
270 # Force Cargo to check that Cargo.lock describes the precise dependency
271 # set that all the Cargo.toml files create, instead of updating it.
274 # Indicate whether the vendored sources are used for Rust dependencies or not
277 # Typically the build system will build the Rust compiler twice. The second
278 # compiler, however, will simply use its own libraries to link against. If you
279 # would rather to perform a full bootstrap, compiling the compiler three times,
280 # then you can set this option to true. You shouldn't ever need to set this
282 #full-bootstrap = false
284 # Enable a build of the extended Rust tool set which is not only the compiler
285 # but also tools such as Cargo. This will also produce "combined installers"
286 # which are used to install Rust and Cargo together. This is disabled by
287 # default. The `tools` option (immediately below) specifies which tools should
288 # be built if `extended = true`.
291 # Set of tools to be included in the installation.
293 # If `extended = false`, the only one of these built by default is rustdoc.
295 # If `extended = true`, they're all included, with the exception of
296 # rust-demangler which additionally requires `profiler = true` to be set.
298 # If any enabled tool fails to build, the installation fails.
307 # "rust-demangler", # if profiler = true
310 # Verbosity level: 0 == not verbose, 1 == verbose, 2 == very verbose
313 # Build the sanitizer runtimes
316 # Build the profiler runtime (required when compiling with options that depend
317 # on this runtime, such as `-C profile-generate` or `-C instrument-coverage`).
320 # Indicates whether the native libraries linked into Cargo will be statically
322 #cargo-native-static = false
324 # Run the build with low priority, by setting the process group's "nice" value
325 # to +10 on Unix platforms, and by using a "low priority" job object on Windows.
326 #low-priority = false
328 # Arguments passed to the `./configure` script, used during distcheck. You
329 # probably won't fill this in but rather it's filled in by the `./configure`
333 # Indicates that a local rebuild is occurring instead of a full bootstrap,
334 # essentially skipping stage0 as the local compiler is recompiling itself again.
335 #local-rebuild = false
337 # Print out how long each rustbuild step took (mostly intended for CI and
338 # tracking over time)
339 #print-step-timings = false
341 # Print out resource usage data for each rustbuild step, as defined by the Unix
342 # struct rusage. (Note that this setting is completely unstable: the data it
343 # captures, what platforms it supports, the format of its associated output, and
344 # this setting's very existence, are all subject to change.)
345 #print-step-rusage = false
347 # Always patch binaries for usage with Nix toolchains. If `true` then binaries
348 # will be patched unconditionally. If `false` or unset, binaries will be patched
349 # only if the current distribution is NixOS. This option is useful when using
350 # a Nix toolchain on non-NixOS distributions.
351 #patch-binaries-for-nix = false
353 # Collect information and statistics about the current build and writes it to
354 # disk. Enabling this or not has no impact on the resulting build output. The
355 # schema of the file generated by the build metrics feature is unstable, and
356 # this is not intended to be used during local development.
359 # =============================================================================
360 # General install configuration options
361 # =============================================================================
364 # Instead of installing to /usr/local, install to this path instead.
365 #prefix = "/usr/local"
367 # Where to install system configuration files
368 # If this is a relative path, it will get installed in `prefix` above
371 # Where to install documentation in `prefix` above
372 #docdir = "share/doc/rust"
374 # Where to install binaries in `prefix` above
377 # Where to install libraries in `prefix` above
380 # Where to install man pages in `prefix` above
381 #mandir = "share/man"
383 # Where to install data in `prefix` above
386 # =============================================================================
387 # Options for compiling Rust code itself
388 # =============================================================================
391 # Whether or not to optimize the compiler and standard library.
392 # WARNING: Building with optimize = false is NOT SUPPORTED. Due to bootstrapping,
393 # building without optimizations takes much longer than optimizing. Further, some platforms
394 # fail to build without this optimization (c.f. #65352).
397 # Indicates that the build should be configured for debugging Rust. A
398 # `debug`-enabled compiler and standard library will be somewhat
399 # slower (due to e.g. checking of debug assertions) but should remain
402 # Note: If this value is set to `true`, it will affect a number of
403 # configuration options below as well, if they have been left
404 # unconfigured in this file.
406 # Note: changes to the `debug` setting do *not* affect `optimize`
407 # above. In theory, a "maximally debuggable" environment would
408 # set `optimize` to `false` above to assist the introspection
409 # facilities of debuggers like lldb and gdb. To recreate such an
410 # environment, explicitly set `optimize` to `false` and `debug`
411 # to `true`. In practice, everyone leaves `optimize` set to
412 # `true`, because an unoptimized rustc with debugging
413 # enabled becomes *unusably slow* (e.g. rust-lang/rust#24840
414 # reported a 25x slowdown) and bootstrapping the supposed
415 # "maximally debuggable" environment (notably libstd) takes
420 # Whether to download the stage 1 and 2 compilers from CI.
421 # This is mostly useful for tools; if you have changes to `compiler/` they will be ignored.
423 # You can set this to "if-unchanged" to only download if `compiler/` has not been modified.
424 #download-rustc = false
426 # Number of codegen units to use for each compiler invocation. A value of 0
427 # means "the number of cores on this machine", and 1+ is passed through to the
430 # Uses the rustc defaults: https://doc.rust-lang.org/rustc/codegen-options/index.html#codegen-units
431 #codegen-units = if incremental { 256 } else { 16 }
433 # Sets the number of codegen units to build the standard library with,
434 # regardless of what the codegen-unit setting for the rest of the compiler is.
435 # NOTE: building with anything other than 1 is known to occasionally have bugs.
436 # See https://github.com/rust-lang/rust/issues/83600.
437 #codegen-units-std = codegen-units
439 # Whether or not debug assertions are enabled for the compiler and standard
440 # library. Debug assertions control the maximum log level used by rustc. When
441 # enabled calls to `trace!` and `debug!` macros are preserved in the compiled
442 # binary, otherwise they are omitted.
444 # Defaults to rust.debug value
445 #debug-assertions = rust.debug (boolean)
447 # Whether or not debug assertions are enabled for the standard library.
448 # Overrides the `debug-assertions` option, if defined.
450 # Defaults to rust.debug-assertions value
451 #debug-assertions-std = rust.debug-assertions (boolean)
453 # Whether or not to leave debug! and trace! calls in the rust binary.
454 # Overrides the `debug-assertions` option, if defined.
456 # Defaults to rust.debug-assertions value
458 # If you see a message from `tracing` saying
459 # `max_level_info` is enabled and means logging won't be shown,
460 # set this value to `true`.
461 #debug-logging = rust.debug-assertions (boolean)
463 # Whether or not overflow checks are enabled for the compiler and standard
466 # Defaults to rust.debug value
467 #overflow-checks = rust.debug (boolean)
469 # Whether or not overflow checks are enabled for the standard library.
470 # Overrides the `overflow-checks` option, if defined.
472 # Defaults to rust.overflow-checks value
473 #overflow-checks-std = rust.overflow-checks (boolean)
475 # Debuginfo level for most of Rust code, corresponds to the `-C debuginfo=N` option of `rustc`.
476 # `0` - no debug info
477 # `1` - line tables only - sufficient to generate backtraces that include line
478 # information and inlined functions, set breakpoints at source code
479 # locations, and step through execution in a debugger.
480 # `2` - full debug info with variable and type information
481 # Can be overridden for specific subsets of Rust code (rustc, std or tools).
482 # Debuginfo for tests run with compiletest is not controlled by this option
483 # and needs to be enabled separately with `debuginfo-level-tests`.
485 # Note that debuginfo-level = 2 generates several gigabytes of debuginfo
486 # and will slow down the linking process significantly.
488 # Defaults to 1 if debug is true
491 # Debuginfo level for the compiler.
492 #debuginfo-level-rustc = debuginfo-level
494 # Debuginfo level for the standard library.
495 #debuginfo-level-std = debuginfo-level
497 # Debuginfo level for the tools.
498 #debuginfo-level-tools = debuginfo-level
500 # Debuginfo level for the test suites run with compiletest.
501 # FIXME(#61117): Some tests fail when this option is enabled.
502 #debuginfo-level-tests = 0
504 # Should rustc be build with split debuginfo? Default is platform dependent.
505 # Valid values are the same as those accepted by `-C split-debuginfo`
506 # (`off`/`unpacked`/`packed`).
508 # On Linux, split debuginfo is disabled by default.
510 # On Apple platforms, unpacked split debuginfo is used by default. Unpacked
511 # debuginfo does not run `dsymutil`, which packages debuginfo from disparate
512 # object files into a single `.dSYM` file. `dsymutil` adds time to builds for
513 # no clear benefit, and also makes it more difficult for debuggers to find
514 # debug info. The compiler currently defaults to running `dsymutil` to preserve
515 # its historical default, but when compiling the compiler itself, we skip it by
516 # default since we know it's safe to do so in that case.
518 # On Windows platforms, packed debuginfo is the only supported option,
519 # producing a `.pdb` file.
520 #split-debuginfo = if linux { off } else if windows { packed } else if apple { unpacked }
522 # Whether or not `panic!`s generate backtraces (RUST_BACKTRACE)
525 # Whether to always use incremental compilation when building rustc
528 # Build a multi-threaded rustc
529 # FIXME(#75760): Some UI tests fail when this option is enabled.
530 #parallel-compiler = false
532 # The default linker that will be hard-coded into the generated
533 # compiler for targets that don't specify a default linker explicitly
534 # in their target specifications. Note that this is not the linker
535 # used to link said compiler. It can also be set per-target (via the
536 # `[target.<triple>]` block), which may be useful in a cross-compilation
539 # See https://doc.rust-lang.org/rustc/codegen-options/index.html#linker for more information.
540 #default-linker = <none> (path)
542 # The "channel" for the Rust build to produce. The stable/beta channels only
543 # allow using stable features, whereas the nightly and dev channels allow using
547 # A descriptive string to be appended to `rustc --version` output, which is
548 # also used in places like debuginfo `DW_AT_producer`. This may be useful for
549 # supplementary build information, like distro-specific package versions.
551 # The Rust compiler will differentiate between versions of itself, including
552 # based on this string, which means that if you wish to be compatible with
553 # upstream Rust you need to set this to "". However, note that if you are not
554 # actually compatible -- for example if you've backported patches that change
555 # behavior -- this may lead to miscompilations or other bugs.
556 #description = <none> (string)
558 # The root location of the musl installation directory. The library directory
559 # will also need to contain libunwind.a for an unwinding implementation. Note
560 # that this option only makes sense for musl targets that produce statically
563 # Defaults to /usr on musl hosts. Has no default otherwise.
564 #musl-root = <platform specific> (path)
566 # By default the `rustc` executable is built with `-Wl,-rpath` flags on Unix
567 # platforms to ensure that the compiler is usable by default from the build
568 # directory (as it links to a number of dynamic libraries). This may not be
569 # desired in distributions, for example.
572 # Prints each test name as it is executed, to help debug issues in the test harness itself.
573 #verbose-tests = false
575 # Flag indicating whether tests are compiled with optimizations (the -O flag).
576 #optimize-tests = true
578 # Flag indicating whether codegen tests will be run or not. If you get an error
579 # saying that the FileCheck executable is missing, you may want to disable this.
580 # Also see the target's llvm-filecheck option.
581 #codegen-tests = true
583 # Flag indicating whether git info will be retrieved from .git automatically.
584 # Having the git information can cause a lot of rebuilds during development.
585 # Note: If this attribute is not explicitly set (e.g. if left commented out) it
586 # will default to true if channel = "dev", but will default to false otherwise.
587 #ignore-git = if channel == "dev" { true } else { false }
589 # When creating source tarballs whether or not to create a source tarball.
592 # After building or testing extended tools (e.g. clippy and rustfmt), append the
593 # result (broken, compiling, testing) into this JSON file.
594 #save-toolstates = <none> (path)
596 # This is an array of the codegen backends that will be compiled for the rustc
597 # that's being compiled. The default is to only build the LLVM codegen backend,
598 # and currently the only standard options supported are `"llvm"`, `"cranelift"`
599 # and `"gcc"`. The first backend in this list will be used as default by rustc
600 # when no explicit backend is specified.
601 #codegen-backends = ["llvm"]
603 # Indicates whether LLD will be compiled and made available in the sysroot for
607 # Indicates whether LLD will be used to link Rust crates during bootstrap on
608 # supported platforms. The LLD from the bootstrap distribution will be used
609 # and not the LLD compiled during the bootstrap.
611 # LLD will not be used if we're cross linking.
613 # Explicitly setting the linker for a target will override this option when targeting MSVC.
616 # Indicates whether some LLVM tools, like llvm-objdump, will be made available in the
620 # Whether to deny warnings in crates
621 #deny-warnings = true
623 # Print backtrace on internal compiler errors during bootstrap
624 #backtrace-on-ice = false
626 # Whether to verify generated LLVM IR
627 #verify-llvm-ir = false
629 # Compile the compiler with a non-default ThinLTO import limit. This import
630 # limit controls the maximum size of functions imported by ThinLTO. Decreasing
631 # will make code compile faster at the expense of lower runtime performance.
632 #thin-lto-import-instr-limit = if incremental { 10 } else { LLVM default (currently 100) }
634 # Map debuginfo paths to `/rust/$sha/...`, generally only set for releases
635 #remap-debuginfo = false
637 # Link the compiler against `jemalloc`, where on Linux and OSX it should
638 # override the default allocator for rustc and LLVM.
641 # Run tests in various test suites with the "nll compare mode" in addition to
642 # running the tests in normal mode. Largely only used on CI and during local
644 #test-compare-mode = false
646 # Global default for llvm-libunwind for all targets. See the target-specific
647 # documentation for llvm-libunwind below. Note that the target-specific
648 # option will override this if set.
649 #llvm-libunwind = 'no'
651 # Enable Windows Control Flow Guard checks in the standard library.
652 # This only applies from stage 1 onwards, and only for Windows targets.
653 #control-flow-guard = false
655 # Enable symbol-mangling-version v0. This can be helpful when profiling rustc,
656 # as generics will be preserved in symbols (rather than erased into opaque T).
657 # When no setting is given, the new scheme will be used when compiling the
658 # compiler and its tools and the legacy scheme will be used when compiling the
660 # If an explicit setting is given, it will be used for all parts of the codebase.
661 #new-symbol-mangling = true|false (see comment)
663 # Select LTO mode that will be used for compiling rustc. By default, thin local LTO
664 # (LTO within a single crate) is used (like for any Rust crate). You can also select
665 # "thin" or "fat" to apply Thin/Fat LTO to the `rustc_driver` dylib.
668 # =============================================================================
669 # Options for specific targets
671 # Each of the following options is scoped to the specific target triple in
672 # question and is used for determining how to compile each target.
673 # =============================================================================
674 [target.x86_64-unknown-linux-gnu]
676 # C compiler to be used to compile C code. Note that the
677 # default value is platform specific, and if not specified it may also depend on
678 # what platform is crossing to what platform.
679 # See `src/bootstrap/cc_detect.rs` for details.
682 # C++ compiler to be used to compile C++ code (e.g. LLVM and our LLVM shims).
683 # This is only used for host targets.
684 # See `src/bootstrap/cc_detect.rs` for details.
687 # Archiver to be used to assemble static libraries compiled from C/C++ code.
688 # Note: an absolute path should be used, otherwise LLVM build will break.
691 # Ranlib to be used to assemble static libraries compiled from C/C++ code.
692 # Note: an absolute path should be used, otherwise LLVM build will break.
693 #ranlib = "ranlib" (path)
695 # Linker to be used to bootstrap Rust code. Note that the
696 # default value is platform specific, and if not specified it may also depend on
697 # what platform is crossing to what platform.
698 # Setting this will override the `use-lld` option for Rust code when targeting MSVC.
699 #linker = "cc" (path)
701 # Path to the `llvm-config` binary of the installation of a custom LLVM to link
702 # against. Note that if this is specified we don't compile LLVM at all for this
704 #llvm-config = <none> (path)
706 # Override detection of whether this is a Rust-patched LLVM. This would be used
707 # in conjunction with either an llvm-config or build.submodules = false.
708 #llvm-has-rust-patches = if llvm-config { false } else { true }
710 # Normally the build system can find LLVM's FileCheck utility, but if
711 # not, you can specify an explicit file name for it.
712 #llvm-filecheck = "/path/to/llvm-version/bin/FileCheck"
714 # Use LLVM libunwind as the implementation for Rust's unwinder.
715 # Accepted values are 'in-tree' (formerly true), 'system' or 'no' (formerly false).
716 # This option only applies for Linux and Fuchsia targets.
717 # On Linux target, if crt-static is not enabled, 'no' means dynamic link to
718 # `libgcc_s.so`, 'in-tree' means static link to the in-tree build of llvm libunwind
719 # and 'system' means dynamic link to `libunwind.so`. If crt-static is enabled,
720 # the behavior is depend on the libc. On musl target, 'no' and 'in-tree' both
721 # means static link to the in-tree build of llvm libunwind, and 'system' means
722 # static link to `libunwind.a` provided by system. Due to the limitation of glibc,
723 # it must link to `libgcc_eh.a` to get a working output, and this option have no effect.
724 #llvm-libunwind = 'no' if Linux, 'in-tree' if Fuchsia
726 # If this target is for Android, this option will be required to specify where
727 # the NDK for the target lives. This is used to find the C compiler to link and
729 # See `src/bootstrap/cc_detect.rs` for details.
730 #android-ndk = <none> (path)
732 # Build the sanitizer runtimes for this target.
733 # This option will override the same option under [build] section.
734 #sanitizers = build.sanitizers (bool)
736 # Build the profiler runtime for this target(required when compiling with options that depend
737 # on this runtime, such as `-C profile-generate` or `-C instrument-coverage`).
738 # This option will override the same option under [build] section.
739 #profiler = build.profiler (bool)
741 # Force static or dynamic linkage of the standard library for this target. If
742 # this target is a host for rustc, this will also affect the linkage of the
743 # compiler itself. This is useful for building rustc on targets that normally
744 # only use static libraries. If unset, the target's default linkage is used.
745 #crt-static = <platform-specific> (bool)
747 # The root location of the musl installation directory. The library directory
748 # will also need to contain libunwind.a for an unwinding implementation. Note
749 # that this option only makes sense for musl targets that produce statically
751 #musl-root = build.musl-root (path)
753 # The full path to the musl libdir.
754 #musl-libdir = musl-root/lib
756 # The root location of the `wasm32-wasi` sysroot. Only used for the
757 # `wasm32-wasi` target. If you are building wasm32-wasi target, make sure to
758 # create a `[target.wasm32-wasi]` section and move this field there.
759 #wasi-root = <none> (path)
761 # Used in testing for configuring where the QEMU images are located, you
762 # probably don't want to use this.
763 #qemu-rootfs = <none> (path)
765 # Skip building the `std` library for this target. Enabled by default for
766 # target triples containing `-none`, `nvptx`, `switch`, or `-uefi`.
767 #no-std = <platform-specific> (bool)
769 # =============================================================================
770 # Distribution options
772 # These options are related to distribution, mostly for the Rust project itself.
773 # You probably won't need to concern yourself with any of these options
774 # =============================================================================
777 # This is the folder of artifacts that the build system will sign. All files in
778 # this directory will be signed with the default gpg key using the system `gpg`
779 # binary. The `asc` and `sha256` files will all be output into the standard dist
780 # output folder (currently `build/dist`)
782 # This folder should be populated ahead of time before the build system is
784 #sign-folder = <none> (path)
786 # The remote address that all artifacts will eventually be uploaded to. The
787 # build system generates manifests which will point to these urls, and for the
788 # manifests to be correct they'll have to have the right URLs encoded.
790 # Note that this address should not contain a trailing slash as file names will
792 #upload-addr = <none> (URL)
794 # Whether to build a plain source tarball to upload
795 # We disable that on Windows not to override the one already uploaded on S3
796 # as the one built on Windows will contain backslashes in paths causing problems
800 # Whether to allow failures when building tools
801 #missing-tools = false
803 # List of compression formats to use when generating dist tarballs. The list of
804 # formats is provided to rust-installer, which must support all of them.
806 # This list must be non-empty.
807 #compression-formats = ["gz", "xz"]