commit | a0eb4481cfd25624a9c37656da0884b83fa6823e | [log] [tgz] |
---|---|---|
author | Sven Zheng <svenzheng@google.com> | Mon Dec 14 21:38:49 2020 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 14 21:38:49 2020 |
tree | 61ef695fc616f25407441791db7e7fc8ede3ca24 | |
parent | 9a41227d1f88b6516da3bdc72c834a68c970d8f5 [diff] |
Reland "[Lacros] Use cfi and thin_lto for Lacros official build" This is a reland of efe87dc0309ca0621780e67c969eb4384d84e715 Original issue was fixed in crrev.com/c/2584633 Locally tested Lacros can build with these gn args. Original change's description: > [Lacros] Use cfi and thin_lto for Lacros official build > > CFI and ThinLTO were disabled on the simple chrome workflow > because they increase build time quite a bit. > But for official build, then should be enabled. > > Bug: 1157567 > Change-Id: I33a9eac37221f31da9a6725b19992d5daded72dc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586085 > Reviewed-by: Yuke Liao <liaoyuke@chromium.org> > Reviewed-by: Sven Zheng <svenzheng@chromium.org> > Commit-Queue: Sven Zheng <svenzheng@chromium.org> > Cr-Commit-Position: refs/heads/master@{#835956} Bug: 1157567 Change-Id: Ib8d009f1e0e8efe8b8c3033086c9df4b6d596175 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2590075 Reviewed-by: Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Sven Zheng <svenzheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#836791}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.