./x.py build --stage 1
# build stage0 libstd
- ./x.py build --stage 0 src/libstd
+ ./x.py build --stage 0 library/std
# build a particular crate in stage0
- ./x.py build --stage 0 src/libtest
+ ./x.py build --stage 0 library/test
```
If files are dirty that would normally be rebuilt from stage 0, that can be
./x.py test src/test/ui --test-args substring-of-test-name
# execute tests in the standard library in stage0
- ./x.py test --stage 0 src/libstd
+ ./x.py test --stage 0 library/std
# execute tests in the core and standard library in stage0,
# without running doc tests (thus avoid depending on building the compiler)
- ./x.py test --stage 0 --no-doc src/libcore src/libstd
+ ./x.py test --stage 0 --no-doc library/core library/std
# execute all doc tests
./x.py test src/doc
The current build is unfortunately not quite as simple as `cargo build` in a
directory, but rather the compiler is split into three different Cargo projects:
-* `src/libstd` - the standard library
-* `src/libtest` - testing support, depends on libstd
+* `library/std` - the standard library
+* `library/test` - testing support, depends on libstd
* `src/rustc` - the actual compiler itself
Each "project" has a corresponding Cargo.lock file with all dependencies, and