| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
We "using namespace std" anywhere we need a std::string or a std::vector.
|
|\
| |
| | |
on windows a network path starts with two backslashes
|
| | |
|
|/
|
|
|
| |
Disable the size_t truncation warning. (Note that this leaves on
the other truncation-related warnings, like int->char.)
|
| |
|
| |
|
|
|
|
|
|
|
| |
This test covers bug fix introduced by 62e9139740. However,
reverting this patch does not trigger a test failure. Maybe, I am
not testing on the right platform (Linux). Anyway, in all cases
I think this test deserves to be added.
|
|
|
|
| |
From a patch from Peter Kuemmel <syntheticpp@gmx.net>.
|
|
|
|
| |
smart terminal.
|
|
|
|
| |
Fixes part of issue 121, but the fix exposed a further issue.
|
|
|
|
|
|
|
|
|
|
|
| |
This allows generating build files in a subdirectory of your source tree.
- Change CanonicalizePath to accept this.
- CanonicalizePath no longer has an error condition, so change it to a void
function.
I profiled the result against Chrome and it might be ~100ms slower, but that
might just be Chrome's size working against me. In any case I think there
are lower-hanging performance fruit elsewhere.
|
|
|
|
|
| |
We frequently do use absolute paths when depfiles refer to
e.g. /usr/include/stdio.h.
|
| |
|
|
Also add util_test.cc and move the CanonicalizePathTest into there.
Signed-off-by: Thiago Farina <tfarina@chromium.org>
|