diff options
| author | bors <bors@rust-lang.org> | 2016-08-28 21:57:51 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-28 21:57:51 -0700 |
| commit | 86dde9bbda92c02c61282b5df5d38338a798ef3b (patch) | |
| tree | 1e357978880abddcaa112a680fb692a6c20e91e9 /src/rustllvm/RustWrapper.cpp | |
| parent | acd3f796d26e9295db1eba1ef16e0d4cc3b96dd5 (diff) | |
| parent | 4b5007a1a25c09746307c9e8cabdc6292f969582 (diff) | |
| download | rust-86dde9bbda92c02c61282b5df5d38338a798ef3b.tar.gz rust-86dde9bbda92c02c61282b5df5d38338a798ef3b.zip | |
Auto merge of #36062 - japaric:smarter-submodules, r=alexcrichton
rustbuild: smarter `git submodule`-ing With this commit, if one bootstraps rust against system llvm then the src/llvm submodule is not updated/checked-out. This saves considerable network bandwith when starting from a fresh clone of rust-lang/rust as the llvm submodule is never cloned. cc #30107 r? @alexcrichton cc @petevine ~~We could also avoid updating the jemalloc submodule if --disable-jemalloc is used. It just hasn't been implemented.~~ Done This probably doesn't handle "recursive" submodules correctly but I think we don't have any of those right now. I'm still testing a bootstrap but already confirmed that the llvm submodule doesn't get updated when `--llvm-root` is passed to `configure`.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions