commit | 2aaf4de55b42f276cc398fb55928b47355feaa89 | [log] [tgz] |
---|---|---|
author | Ken Rockot <rockot@google.com> | Fri Aug 16 05:45:44 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 16 05:45:44 2024 |
tree | ea2946ced5454355e877427a513005712610c336 | |
parent | 36a93cf650533c6badd8da3ca33be4001b3bbf97 [diff] |
Reland "Remove legacy Mojo Core from most build configs" This is a reland of commit 13b1733de755bdc6b324c6888bdcebffde6d5ece The original change was reverted because Windows builds were still configured to package mojo_core.dll with the browser even though we were no longer building it. There are no longer any plans to use this DLL, so patchset 2 here removes all packaging of it. Original change's description: > Remove legacy Mojo Core from most build configs > > Other than Chrome OS and fuzzer builds, we don't need to support this > anymore. Add a new buildflag (mojo_support_legacy_core) which defaults > to false except in those cases, and don't build any of that code > unless it's true. > > Bug: 359926651 > Change-Id: I1c207f2ee55ee28c9920ab6db3e3c2f447eccab2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5789371 > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Commit-Queue: Ken Rockot <rockot@google.com> > Cr-Commit-Position: refs/heads/main@{#1342426} Bug: 359926651 Change-Id: I6624315f3cdd230a51290bc487d33bb6324ca1a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5792219 Reviewed-by: Scott Violet <sky@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Ken Rockot <rockot@google.com> Reviewed-by: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/main@{#1342674}
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.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
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.
If you found a bug, please file it at https://crbug.com/new.