Revert "Android: Always use generated _jni.h files from default toolchain"

This reverts commit a7f7230befa072e62486de49994c9af331de2a34.

Reason for revert: arm64 compile failures crbug.com/1373705

Original change's description:
> Android: Always use generated _jni.h files from default toolchain
>
> Two motivations:
> 1) For target_cpu="arm64", it's wasteful to regenerate these files when
>    building the arm32 libraries for fat apks.
> 2) I'm working on introducing a new toolchain for robolectric tests to
>    use native code, and getting jni generation to work in this toolchain
>    (which has is_android=false) is tricky. It's simpler to re-use the
>    code gen from the default toolchain.
>
> Rather than suffix every dep of a generate_jni target with
> "($default_toolchain)", this changes the generate_jni() template to
> trampoline to the default_toolchain's copy.
>
> Bug: 1369398, 1223993
> Change-Id: I845ed60fa53d617d2b2ab5566b6468cce4271923
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3925477
> Reviewed-by: Dirk Pranke <dpranke@google.com>
> Commit-Queue: Andrew Grieve <agrieve@chromium.org>
> Reviewed-by: Samuel Huang <huangs@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1057481}

Bug: 1369398, 1223993, 1373705
Change-Id: I36e5045446442c35c62c1e2944a473ab496a8930
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3949850
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1058080}
4 files changed
tree: e29f4ad1083d104e55400de33c98f7ea70b1f1e9
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo 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.