commit | 23c4a4f3ba2ddfdab9f6bd6c5983a4af4715b139 | [log] [tgz] |
---|---|---|
author | sbingler <bingler@chromium.org> | Thu Nov 03 17:00:13 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 03 17:00:13 2022 |
tree | b1ab23e6666c9b8a55e3dc506ccb60624115fbd4 | |
parent | a75b68977b3f13eb95e4625cc365b36358710d41 [diff] |
Add exports to runtime feature state mojo build The generation step was missing export tags, meaning that anything outside their component that needed them would fail to link. This CL adds the tags. Bug: 1377000 Change-Id: Ibf6c631622915c5b4393a5e6c4d71d03b7511b27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4000661 Commit-Queue: Steven Bingler <bingler@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1067069}
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.