| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
prints the rate of finished edges per second to the console,
for instance with NINJA_STATUS="[%s/%t %o(%c)/s] ":
[132/1922 16.1(14)/s]
16.1 is the average for all processed files (here 132 since start)
14 is the average of the last n files while n is the number specifies by
-j (or its default)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As described on https://github.com/martine/ninja/pull/349 , this test
shouldn't have been passing. Fixing a Valgrind issue showed that the
test was wrong. Thankfully it wasn't a critical issue.
The new code verifies that we either succeed or report an error when
parsing -- the only behavior we really care about is not crashing.
|
| | | |
| | | |
| | | |
| | | | |
Not a real problem, mainly to make valgrind happy
|
| | | |
| | | |
| | | |
| | | | |
From a patch from Claus Klein <claus.klein@arcormail.de>.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
https://github.com/martine/ninja/issues/360
Signed-off-by: Thiago Farina <tfarina@chromium.org>
|
|\ \ \ \
| | | | |
| | | | | |
windows: use WriteConsoleOutput instead of printf to avoid moving cursor
|
| | | | | |
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It turns out to be trickier than expected to process these correctly.
It turns out to also be trickier than expected to give a nice error
message on encountering these. But the behavior prior to this patch
would just be silent failures where we attempted to examine paths
that accidentally contained embedded \r.
For now, fix all regexes of the form [^...] to include \r in the
excluded block, then assert that we get a vague lexer error near the
problem.
In the future perhaps we can open manifest files in text mode on Windows
or just disallow Windows-style CRLF in the manual.
|
| | | |
| | | |
| | | |
| | | | |
Patch from Scott Graham <scottmg@chromium.org>.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
I think it might have been an oversight that this was marked
Linux-specific.
|
|\ \ \ \
| | | | |
| | | | | |
fix win32 compile, fix BuildLogTest.WriteRead on 2nd run
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Add missing include of <sys/resouce.h>
|
| | |/ / /
| |/| | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
https://github.com/martine/ninja/issues/358
Signed-off-by: Thiago Farina <tfarina@chromium.org>
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Attempting to compile with g++ 4.1.2 failed because the POLLRDHUP
constant was not defined when <poll.h> is included.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
So it matches with the class name in there.
Signed-off-by: Thiago Farina <tfarina@chromium.org>
|
|\ \ \ \
| |_|_|/
|/| | | |
Do not reset restat_mtime if an input is missing
|
| | | | |
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
- Edge::Dump could crash if called while inputs_ is being extended
- Node::Dump prints Node attributes, in-edge and lists of out-edges
- Dump functions now accept "prefix" parameter, printed along with the object
for easier orientation. For example, edge->Dump("Re-reading deps files").
|
| | |
| | |
| | |
| | |
| | |
| | | |
Nico convinced me that it's safe to do this without revving the build
log format: the old decimal values will still parse as hex (just as
different numbers) and cause a superfluous rebuild.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Log format 4 was introduced in January.
There's been plenty of time to migrate.
|
| | |
| | |
| | |
| | | |
Fixes a warning.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
No need to write 'struct' before type name when declaraing variables in ...
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Thiago Farina <tfarina@chromium.org>
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
.build_log load time 350ms -> 17ms, filesize 197MB -> 1.6MB on
Mac. On Windows, it's 500ms -> 20ms.
Makes the build log a lot less useful for scripts, but there could
be a tool for use cases that need log information. A prototype of
such a tool is in https://github.com/nico/ninja/commit/1b243d311
The hash function is 64bit murmurhash2. Assuming that that different
commands get the same hash only by chance, it's is very unlikely
for two different commands to hash to the same value with a 64bit
hash.
|
|\ \ \
| | | |
| | | | |
add canon_perftest
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Fixes issue #327.
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Cleanups
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | | |
total_time was always -1, because it computed a pointer difference,
not a time difference (should've been |*end_time - *start_time|).
|
|\ \ \
| | | |
| | | | |
Remove unused variable last_update_millis_.
|