commit | 091930a04ab79f41adcab437c2bb61b9741b6042 | [log] [tgz] |
---|---|---|
author | Byungwoo Lee <blee@igalia.com> | Tue Mar 04 00:39:26 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 04 00:39:26 2025 |
tree | 5bfed24c92a12291139e696fa160ae37af7bb140 | |
parent | ef8b763ec820354d29babc475dc560eb65c37028 [diff] |
Fix build with safe_browsing_mode=0 (5/5) Fix the `safe_browsing_mode=0` build by guarding header includes and related codes using `BUILDFLAG(SAFE_BROWSING_AVAILABLE)`. This CL is a part of the build fix that guards following header inclusions under the flag: - chrome/browser/safe_browsing/ - download_protection/download_protection_service.h - safe_browsing_service.h - components/safe_browsing/content/renderer/ - phishing_classifier/phishing_model_setter_impl.h - renderer_url_loader_throttle.h - websocket_sb_extensions_handshake_throttle.h guards following build dependency under `safe_browsing_mode==0` condition: - //components/safe_browsing/content/browser:client_side_detection_service and remove guards for the following build targets to avoid header inclusion error: - //components/safe_browsing/content/common/proto:download_file_types_proto - download_file_types.proto Low-Coverage-Reason: TRIVIAL_CHANGE This change contains only minor build fix. Bug: 390205854 Change-Id: I9a56bbf5c5362096a3dea16f0b755b78e1fcf902 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6184185 Commit-Queue: Byungwoo Lee <blee@igalia.com> Reviewed-by: Lily Chen <chlily@chromium.org> Reviewed-by: Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/main@{#1427470}
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.