Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | depfile_parser: remove restriction on multiple outputs | Ben Boeckel | 2019-11-20 | 1 | -11/+2 |
| | |||||
* | Restore depfile toleration of multiple output paths on distinct lines | Brad King | 2018-11-19 | 1 | -0/+17 |
| | | | | | | | | | | | | | | | | Prior to introduction of depfile parser handling of multiple rules, ninja silently accepted a depfile of the form: out: in1 in2 in3 other: otherIn1 otherIn2 otherIn3 and incorrectly treated `other` and `otherIn*` as additional inputs to `out`. Now we prefer to reject this just as we already do for a depfile specifying multiple outputs on one line. However, this can break existing cases where such a depfile was silently tolerated. Add a `-w depfilemulti={err,warn}` option to control this behavior, and make it just a warning by default. | ||||
* | Header guards were missing from some header files. | Jonathan Sternberg | 2012-05-30 | 1 | -0/+5 |
| | |||||
* | de-escape backslashes in depfiles while parsing | Evan Martin | 2011-12-28 | 1 | -2/+3 |
| | |||||
* | switch DepfileParser to take a string* to make memory clearer | Evan Martin | 2011-12-27 | 1 | -1/+4 |
| | | | | Add some comments as well. | ||||
* | use re2c to parse depfiles | Evan Martin | 2011-12-07 | 1 | -0/+26 |