summaryrefslogtreecommitdiffstats
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
...
* document depsEvan Martin2013-04-091-16/+83
|
* tag a feature with the right version numberEvan Martin2013-04-051-1/+1
|
* Merge pull request #513 from fifoforlifo/masterEvan Martin2013-03-111-1/+2
|\ | | | | Adding elapsed time (%e) to NINJA_STATUS.
| * Added %e to manual.asciidoc, fixed brace style.Avinash Baliga2013-03-111-1/+2
| |
* | Merge pull request #512 from pcc/compilation-databaseEvan Martin2013-03-101-0/+6
|\ \ | | | | | | Add compdb tool
| * | Add compdb toolPeter Collingbourne2013-03-101-0/+6
| |/ | | | | | | | | This tool helps convert Ninja build files to a compilation database of the form used by Clang tooling.
* | Merge pull request #499 from lht/patch-1Evan Martin2013-03-101-2/+2
|\ \ | | | | | | Fix typo in manual
| * | Fix typo in manualHaitao Li 李海涛2013-02-171-2/+2
| | |
* | | Fix typo, s/verison/version/Martin Olsson2013-02-191-1/+1
| |/ |/|
* | manual: move in_newline to the referenceEvan Martin2013-02-191-15/+19
| | | | | | | | It's a detail, it doesn't belong in the brief tutorial overview.
* | add versioning notes to features in the manualEvan Martin2013-02-171-3/+3
| | | | | | | | This helps guide which ninja version to depend on.
* | make doc xrefs link to section headersEvan Martin2013-02-171-7/+5
|/
* rearrange env variable section layoutEvan Martin2013-02-171-12/+14
|
* move from asciidoc html to asciidoc -> docbook -> htmlEvan Martin2013-02-172-0/+46
| | | | | As best as I can tell this is the easiest way to customize the asciidoc HTML output.
* docs for ninja_required_versionEvan Martin2013-02-161-0/+44
| | | | (And some extra docs for top-level variables in general.)
* mark pools as experimental in the docsEvan Martin2013-02-011-0/+4
|
* drop the "rules" tool completelyEvan Martin2012-12-291-4/+0
| | | | | I had already broken this earlier, but the refactor of variable handling broke it completely.
* update docs to clarify scoping rulesEvan Martin2012-12-291-17/+35
|
* NINJA_STATUS: add support of `%p` for percentageyannicklm2012-12-141-0/+1
|
* Improve the manual documentationRobert Iannucci2012-11-301-10/+12
|
* add docsRobert Iannucci2012-11-101-0/+51
|
* document that \r and \t are disallowedEvan Martin2012-08-101-1/+3
| | | | Finishes #394.
* Merge pull request #351 from syntheticpp/rateEvan Martin2012-07-271-0/+2
|\ | | | | print edges per second
| * print edges per secondPeter Kuemmel2012-07-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | 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)
* | fix manual to reflect reality of depfile cleaningEvan Martin2012-07-171-3/+3
|/ | | | Fixes issue #362.
* add $in_newlineScott Graham2012-06-151-2/+5
|
* Minor spelling fixes in manual.Nico Weber2012-05-131-3/+3
|
* clarify what i mean by "policy"Evan Martin2012-05-081-2/+8
|
* mention reactosEvan Martin2012-05-041-3/+4
|
* mention platform supportEvan Martin2012-05-041-2/+12
|
* add $: to docsEvan Martin2012-05-021-1/+5
|
* Fix a link to Google+.Hiroyuki Iwatsuki2012-04-281-1/+1
|
* rearrange the manualEvan Martin2012-04-271-127/+208
| | | | | | | | | My goals were: - shorten the introductory text, hopefully quickly answering the "why?" question first. - put the information relevant to ninja users (e.g. people using CMake who don't especially care about ninja) next, at the beginning. - consolidate the "generating ninja files" text below.
* doc encoding supportEvan Martin2012-04-261-0/+4
|
* Merge pull request #278 from tychoish/masterEvan Martin2012-04-261-1/+3
|\ | | | | Minor Documentation Tweak
| * docs: clarifying that there can be only one command per ruletycho garen2012-04-241-1/+3
| |
* | Introduce NINJA_STATUS env var for customization.Nicolas Despres2012-04-241-0/+17
|/ | | | | | Some people may want to display different relevant information about the progress of the build. Also it can be usefull to debug jobs allocation.
* adjust rspfile docs to properly renderEvan Martin2012-03-061-16/+16
|
* Response filesunknown2012-02-091-0/+20
|
* Fix typo in manual.Nicolas Despres2011-12-301-1/+1
|
* move some docs to home pageEvan Martin2011-12-281-50/+10
|
* link to blog post in docsEvan Martin2011-12-281-5/+6
|
* rearrange manual to centralize quoting rulesEvan Martin2011-12-201-29/+46
|
* move build/install to READMEEvan Martin2011-12-061-17/+1
|
* remove reference to nonexistent fileEvan Martin2011-12-051-2/+0
|
* prettify manual for toolsEvan Martin2011-12-051-21/+31
|
* minor manual touchupsEvan Martin2011-12-051-13/+15
|
* Add a "commands" toolPeter Collingbourne2011-11-041-0/+4
| | | | | | | | | | | | | | | This tool performs a post-order traversal of the build graph, starting from a list of targets specified on the command line, and for each build statement encountered, prints the evaluated command line. Use cases include: - Generating input for a tool which needs to know the full command line for every command invoked during a build. Many static analysis and indexing tools require this information. - Generating a build script which does not depend on Ninja. For example, such a script could be used by Ninja to bootstrap itself.
* Implement restat rulesPeter Collingbourne2011-10-241-0/+6
| | | | | | | | | | | | | | | | | A restat rule is a rule which is capable of pruning the build tree depending on the timestamps of its outputs before and after a build. After a restat rule is rebuilt, Ninja will re-stat each output file to obtain its current timestamp. If the timestamp is unchanged from when Ninja initially stat'ed the file before starting the build, Ninja will mark that output file as clean, and recursively for each reverse dependency of the output file, recompute its dirty status. Ninja then stores the most recent timestamp of any input file in the build log entry associated with the output file. This timestamp will be treated by future invocations of Ninja as the output file's modification time instead of the output file's actual modification time for the purpose of deciding whether it is dirty (but not whether its reverse dependencies are dirty).
* Implement Make-style order-only dependenciesPeter Collingbourne2011-10-241-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the implementation of order-only dependencies differed between Make and Ninja in two important ways: 1) If the order-only dependency existed but was out of date, it would never be rebuilt, whereas Make would always rebuild out of date order-only dependencies. 2) If the order-only dependency did not exist, it would cause its reverse dependencies to always build, whereas Make would only rebuild a file if a non-order-only dependency was out of date. A key distinction between Ninja and Make as seen through the above two points was that in Ninja, order-only dependencies cared about whether the target as a file exists (so perhaps a better name for the old semantics would have been "missing-only dependencies"). These differences made it impossible to introduce an order-only dependency on an always out-of-date (i.e. missing) target without also causing the depender and its reverse dependencies to rebuild unnecessarily on every build. Build systems which must perform some action (such as logging the build start time, or printing a message) at the start of every build typically implement this by adding to every target an order-only dependency which performs this action, which would have forced an entire rebuild on every invocation of Ninja under the old semantics. This commit causes Ninja to conform to the Make-style behaviour.
generated by cgit v0.12 at 2024-07-16 08:58:54 (GMT)