commit | 6f773ca0c8a7ce64a37498725632de0f4a2de6b1 | [log] [tgz] |
---|---|---|
author | Sam Maier <smaier@chromium.org> | Wed May 10 19:58:09 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 10 19:58:09 2023 |
tree | 1460cfc281185209e065aea923b531de200d19cf | |
parent | 4178735e7abe99ca33cbd9fd67a1ad54c96b6a61 [diff] |
Revert "JNI: Only using 1 registration per apk" This reverts commit a74d255224ea190cdfa0f9bb42d0e2791fd907a7. Reason for revert: broke internal bots Original change's description: > JNI: Only using 1 registration per apk > > We now associate a JNI registration with a native library, via our new > native_with_jni template. We no longer have a generate_jni_registration > happening with pure Java in the apk template. > > We now only output 1 GEN_JNI per srcjar, and instead of collecting all > JNI from modules and outputting many GEN_JNIs in one srcjar. > > Bug: 1406611 > Change-Id: Iec40dc7c443e206f177fa8a7d5f9635cefa4c747 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4219332 > Commit-Queue: Sam Maier <smaier@chromium.org> > Owners-Override: Sam Maier <smaier@chromium.org> > Reviewed-by: Andrew Grieve <agrieve@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1142236} Bug: 1406611 Change-Id: Ifedf95de229bd16039ae026dfe3ccc90b66f154c No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4518235 Commit-Queue: Lijin Shen <lazzzis@google.com> Auto-Submit: Sam Maier <smaier@chromium.org> Reviewed-by: Lijin Shen <lazzzis@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Lijin Shen <lazzzis@google.com> Cr-Commit-Position: refs/heads/main@{#1142294}
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.