| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
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.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
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.
|
| |
| |
| |
| | |
The two columns of the table run together, making it hard to read.
|
| |
| |
| |
| |
| |
| | |
- Fix the manual build rules (missing the .xsl as an input).
- Add a README describing how the docs build works.
- Add rules that generate PDF, just 'cause we can.
|
| |
| |
| |
| | |
In particular, this helps web search engines index it.
|
| | |
|
|/
|
|
|
|
|
|
| |
Ninja does resolve relative paths and file system links in paths.
Therefore, such paths pointing to the same file will not match and may
lead to an invalid dependency graph.
Signed-off-by: Fredrik Medley <fredrik.medley@gmail.com>
|
| |
|
|\
| |
| | |
Document target^ syntax.
|
| |
| |
| |
| | |
Added a note into the documentation about interesting target^ syntax
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #730. This has always been broken, but due to #690 more paths are now
escaped (e.g. paths containing + characters, like file.c++). Also see
discussion in #689.
The approach is to give EdgeEnv an enum deciding on whether or not to escape
file names, and provide functions that evaluate depfile and rspfile with that
set that to kNoEscape. (depfile=$out.d doesn't make sense on edges with
multiple outputs.)
This should be relatively safe, as $in and $out can't be used on edges, only
on rules (#687).
|
| |
|
|
|
|
|
|
|
| |
This is a pre-defined pool with a depth of 1. It has the special property
that any task in the pool has direct access to the console. This can be
useful for interactive tasks or long-running tasks which produce status
updates on the console (such as test suites).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The earlier section is a tutorial-style overview. The latter section
is for side features like phony rules and header dependencies. Pools
fit in with the latter.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Drop the timing info, it's too variable to commit to a manual.
|
| |
|
| |
|
| |
|
|\
| |
| | |
Adding elapsed time (%e) to NINJA_STATUS.
|
| | |
|
|\ \
| | |
| | | |
Add compdb tool
|
| |/
| |
| |
| |
| | |
This tool helps convert Ninja build files to a compilation database
of the form used by Clang tooling.
|
|\ \
| | |
| | | |
Fix typo in manual
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| | |
It's a detail, it doesn't belong in the brief tutorial overview.
|
| |
| |
| |
| | |
This helps guide which ninja version to depend on.
|
|/ |
|
| |
|
|
|
|
|
| |
As best as I can tell this is the easiest way to customize
the asciidoc HTML output.
|
|
|
|
| |
(And some extra docs for top-level variables in general.)
|
| |
|
|
|
|
|
| |
I had already broken this earlier, but the refactor of variable handling
broke it completely.
|
| |
|
| |
|