7ca140f744
There are a number of config items defined by the chromium_android
module for the chromium and chromium_android module. Previously, config
items for the chromium module were defined that used config_vars to set
specific kwargs for the chromium module config. Additionally, there were
some low-value configs that simply included other configs without
introducing a cohesive concept (e.g. main_builder_mb includes
main_builder and mb). In most cases, there was a config item with the
same name defined for both the chromium and chromium_android modules
because the android builders relied on the chromium config of the same
name as the specified chromium_android config automatically being used
via chromium_android.configure_from_properties.
The chromium_android.configure_from_properties method has been removed
and the chromium configs no longer set config_vars, so many of the
existing config items now provide little value. Removing references to
them will enable removing the config items themselves.
(cherry picked from commit cc108d224a)
Bug: 403607431
Change-Id: Id14f8e40fc41f56c1f34e6c619d03d62588256d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6405179
Reviewed-by: Haiyang Pan <hypan@google.com>
Commit-Queue: Garrett Beaty <gbeaty@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1442203}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6430462
Auto-Submit: Garrett Beaty <gbeaty@google.com>
Commit-Queue: Haiyang Pan <hypan@google.com>
Cr-Commit-Position: refs/branch-heads/7049@{#1732}
Cr-Branched-From: 2dab7846d0951a552bdc4f350dad497f986e6fed-refs/heads/main@{#1427262}
v8
@ e2591684c4
Chromium
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.