commit | 894986a9e6b929029cf32982ff225ccab8233790 | [log] [tgz] |
---|---|---|
author | Scott Graham <scottmg@chromium.org> | Thu Jun 14 14:15:50 2018 -0700 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jun 15 23:41:49 2018 +0000 |
tree | 390c3018966956b9d425fcbff394ce1364f1f748 | |
parent | 64a164c1e8079f7f5db443d423426c99c9394dc3 [diff] |
Big purge of base - Delete AtExit, FilePathWatcher, MemoryMappedFile, MessageLoop, TaskScheduler, most of threading/ - Delete third_party/libevent, third_party/dmg_fp (this makes the json reader not-exactly-json any more because it doesn't support doubles, but GN already disallowed doubles.) - Add src/msg_loop.*. After all the deleting and mucking around, a simple perf comparison against the current in-tree Chrome gn: c:\src\gn>python build\full_test.py \src\cr\src out\wi\gn.exe ninja: Entering directory `out' ninja: no work to do. [430/430] XmlElementWriter.TestXmlEscape PASSED Confirming output matches... Comparing performance... (takes a while) In-tree gn avg: 13.522s Our gn avg: 11.822s This isn't rock-solid, but it seems like it's at least not slower. Change-Id: Id956ffdbb909b1398465098d349b57e10589b27d Reviewed-on: https://gn-review.googlesource.com/1600 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by: Brett Wilson <brettw@chromium.org>
GN is a meta-build system that generates build files for Ninja.
Get started with:
git clone https://gn.googlesource.com/gn cd gn python build/gen.py ninja -C out