about summary refs log tree commit diff
path: root/src/test/run-pass/thinlto
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2017-06-08 22:21:29 +0000
committerbors <bors@rust-lang.org>2017-06-08 22:21:29 +0000
commit9454dd5d2d8786d6eef07e2a7b737ad092e303df (patch)
tree0ebd8426f8d54bc0ebd95cdbbd66999d3c8e1206 /src/test/run-pass/thinlto
parent148e9171481da43738d7d7a79c5e6f7bc2c2ccde (diff)
parent7359c791b50ebe0fa7ccf48faf5a272491c779e3 (diff)
downloadrust-9454dd5d2d8786d6eef07e2a7b737ad092e303df.tar.gz
rust-9454dd5d2d8786d6eef07e2a7b737ad092e303df.zip
Auto merge of #42491 - RalfJung:bootstrap-help, r=alexcrichton
bootstrap: improve 'build --help' by explaining what exactly the last example does

I recently found myself confused about what exactly gets built how often when I run which command; I think this would have helped me.

One thing I did not touch, but I feel could also be improved, is the wording just above: "For a quick build with a usable compile, you can pass".  I am not a native speaker, but this sounds odd to me. Do you mean "For a quick build of a usable compiler" (but then it should say where the usable compiler is produced)? Or do you mean "For a quick build testing if the compiler is usable"? I can reword this, but I'd like to make sure I understand the intent of the message.

What about
```
    For a quick build of a usable compiler, you can pass:

        ./x.py build --stage 1 src/libtest

    This will first build everything once (like --stage 0 without further
    arguments would), and then use the compiler built in stage 0 to build
    src/libtest and its dependencies.
    Once this is done, build/$ARCH/stage1 contains a usable compiler.
```
However, I am not sure this is actually true. In particular, why even bother building the libstd in stage 1? AFAIK that ends up in `build/*/stage1-std`, not in `build/*/stage1` (which is filled from `build/*/stage0-*`).
Diffstat (limited to 'src/test/run-pass/thinlto')
0 files changed, 0 insertions, 0 deletions