[reland] Enable *building* Rusty QR Code Generation on Android and Linux

This is a reland of the core part of https://crrev.com/c/4509543.  The
reland has been made possible by the following fixes:
- https://crrev.com/c/4636942 (split out from the original CL)
- https://crrev.com/c/4633412
- https://crrev.com/c/4634895

This CL enables *building* of Rusty QR Code Generation on the same
platforms and configs where `enable_rust_crash` is built.  It changes
both `enable_rust_qr` and `enable_rust_base_conversions`, because
QR-related FFI requires conversions from `base::span<T>` into
`rust::Slice<T>`.

This CL does *not* yet *use* Rusty QR Code Generation at runtime,
because the "RustyQrCodeGenerator" feature remains disabled by default.

Since this CL starts to include the `third_party/rust/qr_code` library,
it expectedly leads to a ~22kB binary size increase.  This increase has
been reviewed and approved when the ATLs have reviewed landing of the
third-party library (see https://crrev.com/c/4497329 and the approvals
listed from that other CL's description).  Also note that evaluating the
binary size impact of shipping Rust code is tricky, because the cost of
the base C++ libraries is amortized across multiple components, while
the cost of the base Rust libraries will initially only support the QR
crate.

Bug: 1431991
Binary-Size: Size increase is unavoidable (see above).
Change-Id: I380d904f5370d5ee129179abd0a0b949474b53cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4632898
Reviewed-by: Adrian Taylor <adetaylor@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Commit-Queue: Ɓukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1161494}
2 files changed
tree: 3769a7358ad197eb9e5e8cfcd97921d954bede0d
  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. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  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.