diff options
| author | Jan Niklas Hasse <jhasse@bixense.com> | 2018-12-20 12:58:09 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-12-20 12:58:09 +0100 |
| commit | 6e02ebc4b5947095fa64b5bf814f14dd6f6f6a9a (patch) | |
| tree | 9ba80d6d284761890e58202530eb70ae9f6bd23b | |
| parent | b735f796cd00c7f49531e248961fd9c4bde04404 (diff) | |
| download | ninja-6e02ebc4b5947095fa64b5bf814f14dd6f6f6a9a.tar.gz | |
Remove outdated part about Chrome download, fix #1338
| -rw-r--r-- | HACKING.md | 14 |
1 files changed, 3 insertions, 11 deletions
@@ -109,17 +109,9 @@ build "all" before committing to verify the other source still works! ## Testing performance impact of changes -If you have a Chrome build handy, it's a good test case. Otherwise, -[the github downoads page](https://github.com/ninja-build/ninja/releases) -has a copy of the Chrome build files (and depfiles). You can untar -that, then run - - path/to/my/ninja chrome - -and compare that against a baseline Ninja. - -There's a script at `misc/measure.py` that repeatedly runs a command like -the above (to address variance) and summarizes its runtime. E.g. +If you have a Chrome build handy, it's a good test case. There's a +script at `misc/measure.py` that repeatedly runs a command (to address +variance) and summarizes its runtime. E.g. path/to/misc/measure.py path/to/my/ninja chrome |