| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The call to StatIfNecessary in DependencyScan::RecomputeOutputsDirty was
added by commit v1.4.0^2~7^2~1 (Share more code between CleanNode() and
RecomputeDirty(), 2013-09-02) while consolidating code paths. However,
it was needed only when called from RecomputeDirty because prior to
refactoring the CleanNode code path did not call it.
Later commit v1.6.0^2~46^2 (Let DependencyScan::RecomputeDirty() work
correclty with cyclic graphs, 2014-12-07) added back to RecomputeDirty a
loop over outputs that calls StatIfNecessary. Therefore
RecomputeOutputsDirty no longer needs to call StatIfNecessary for either
of its own callers.
|
|\
| |
| | |
Fix ambiguous call to set_terminate on Windows platform
|
|/
|
|
|
|
|
| |
On Windows set_terminate() could either be the standard C++ one or (actually the same one but in the global namespace) the CRT one declared in corecrt_terminate.h
Hence this ambiguity - this patch solves it.
Signed-off-by: g4m4 <misept.dieseneuf@gmail.com>
|
|\
| |
| | |
Add support for implicit outputs in ninja_syntax.py.
|
| | |
|
|\ \
| |/
|/| |
Add link to mailing list
|
|/
|
| |
As a convenience to new users, provide a link to the mailing list.
|
|\
| |
| | |
win: Only drop /showIncludes in bootstrap builds.
|
| |
| |
| |
| | |
Fixes #1103.
|
|\ \
| | |
| | | |
disable warning about conditional expressions
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The standard headers for Visual Studio 2008 generate a warning about
constant conditional expressions when compiled with exception support
disabled. This is caused by the _CATCH_ALL macro in xstddef which is
defined thusly:
#ifdef _HAS_EXCEPTIONS
#define _CATCH_ALL } catch (...) {
#else
#define _CATCH_ALL } if (0) {
#endif
|
|\ \
| | |
| | | |
Minor updates to the manual.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Update link to Chromium's ninja docs (fixes #1038)
* Update cmake URL to what it redirects to, and mention that ninja
is well-supported on all platforms in newer CMake versions.
* Let "others" link to the wiki page listing generators.
|
|\ \ \
| | | |
| | | | |
Print output file on failure
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Modify the FAILED: output to provide the output files that failed to
build, followed by the failed command on the next line. This makes the
failure much easier to read, as you can immediately see much shorter
name of the file that failed instead of trying to parse a very long
command line. It also makes manually re-running the failed command much
easier because you can copy the whole line without ending up with the
FAILED: prefix.
|
|\ \ \ \
| |_|/ /
|/| | | |
Add support for build statement implicit outputs
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some build rules produce outputs that are not mentioned on the command
line but that should be part of the build graph. Such outputs should
not be named in the `$out` variable. Extend the build statement syntax
to support specification of implicit outputs using the syntax
`| out1 out2` after the explicit outputs and before the `:`.
For example, compilation of a Fortran source file `foo.f90` that defines
`MODULE FOO` may now be specified as:
rule fc
command = f95 -c $in -o $out
build foo.o | foo.mod: fc foo.f90
The `foo.mod` file is an implicit output generated by the compiler based
on the content of the source file and not mentioned on the command line.
|
|\ \ \ \
| | | | |
| | | | | |
Deduplicate disk abstraction infrastructure
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Avoid having two separate filesystem interfaces. Simplify test
infrastructure by avoiding custom `ManifestParser::FileReader`
implementations.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Return a status so callers can distinguish a missing file from an empty
file. This allows our VirtualFileSystem test infrastructure to report
as missing any file for which it has no entry.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some clients will need only the ability to read files, so provide this
as a more narrow interface than the full disk interface.
|
|\ \ \ \ \
| |/ / / /
| | / / /
| |/ / /
|/| | | |
perftest: fix compilation after dupe_edge_should_err change
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix some ManifestParser constructor calls missed by commit 56bab441b7
(dupe_edge_should_err from bool to enum, 2016-01-27).
|
|\ \ \ \
| |/ / /
|/| | | |
Canonicalize "." to "."
|
| | | |
| | | |
| | | |
| | | |
| | | | |
"." is a legal path, if the string is empty after canonicalization
return ".".
|
|\ \ \ \
| | | | |
| | | | | |
dupe_edge_should_err from bool to enum
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Add -d keepdepfile to preserve depfiles
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
This is useful when you are developing a tool which generates
GCC-style depfiles.
|
|\ \ \ \
| | | | |
| | | | | |
Make dupbuild=err work in subninja
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
fix for localized version of cl.exe
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Remove unnecessary `std::`
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Use container-based infrastructure for travis-ci.
|
|/ / / /
| | | |
| | | |
| | | | |
To start up faster.
|
|\ \ \ \
| | | | |
| | | | | |
use the default font size for manual headings
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
The third-level subsection headings were almost indistinguishable
from the second-level ones. Fix this by just using the default
styling.
|
|\ \ \ \
| | | | |
| | | | | |
add a section to the manual discussion the command= variable
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
This includes a mention of using cmd /c on Windows.
This would have helped on issue #1070 for example.
|
|\ \ \ \
| | | | |
| | | | | |
Teach zsh to complete intermediary targets.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bash completion script uses "-t targets all" to list the target which
is faster than "-t targets" and reports intermediary targets
(see the manual entry for the 'targets' tool).
See commit fc135c45.
|
|\ \ \ \
| | | | |
| | | | | |
Do not attempt to rebuild infinitely in dry-run mode.
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Fix wrapping file paths in Writer.comment
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As pointed out by nico, we should unconditionally disable breaking of
long words in comments. It is unlikely long words that are in comments
should be split (like pathnames).
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Long file names, especially with hyphens will get incorrectly wrapped by
the comment method. Pass has_path=True to prevent this type of wrapping.
This is mainly so that longer path names can show up in comments on
their on line without breaking them up.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
make use of Bindings typedef
|