diff options
| author | bors <bors@rust-lang.org> | 2013-05-29 15:10:42 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-05-29 15:10:42 -0700 |
| commit | bd30285c8467b33b6fea16be79198f7492107af3 (patch) | |
| tree | 56c10aea0356f19c9304fa1036bfa2c649debdcf /src/libstd/os.rs | |
| parent | 35655a0fb3bde60985d5f92437a729c37bb8755a (diff) | |
| parent | 2b083373e4ac973bad8e3c2b949d6c12991bd623 (diff) | |
| download | rust-bd30285c8467b33b6fea16be79198f7492107af3.tar.gz rust-bd30285c8467b33b6fea16be79198f7492107af3.zip | |
auto merge of #6813 : pnkfelix/rust/fsk-issue-6805-ccache-support, r=catamorphism
Fix #6805: add --enable-ccache configure option to prefix compiler invocations with `ccache` to attempt to reuse common results, e.g. for LLVM (re)builds. The information at developer [Note-ccache](../../wiki/Note-ccache) and at [ccache and clang concerns](http://petereisentraut.blogspot.fr/2011/09/ccache-and-clang-part-2.html) were what drove my introduction of the `-Qunused-arguments` and `CCACHE_CPP2` options. (Though I did confirm first-hand that at least the first really is necessary.) Yes, one certainly can re-route how `gcc` and `clang` are resolved in one's PATH and use that as a way to invoke `ccache`. But I personally do not want to introduce that change to my own PATH, and this seems like a small enough change that it does not hurt to add it, at least for now. (I don't know what form it would take when we move over to `rustpkg`.)
Diffstat (limited to 'src/libstd/os.rs')
0 files changed, 0 insertions, 0 deletions
