Make the frontend_server validate kernel files more strictly (#29497)

This change will make Flutter's frontend_server validate that any kernel
file given to it was produced by the same Dart SDK hash as the
frontend_server itself is based upon.

Notice that this implies one cannot use the prebuilt Dart SDK's
frontend_server and give it kernel files produced in the current build
iff //third_party/dart is at a different SDK hash. (By-default the
prebuilt Dart SDK and //third_party/dart are based on the same git
commit hash)

=> This is mainly relevant for people who change //third_party/dart
   during local development (e.g. for preparing rolls, ...)

=> In such cases one should pass "--no-prebuilt-dart-sdk" to
   flutter/tools/gn

The effect of this change is that one will get a clear message on
mismatched kernel files instead of possibly an exception from the CFE.

The change is changing the Flutter build actions similar to how [0]
changed the Dart build actions.

Issue https://github.com/flutter/flutter/issues/92679

[0] https://dart-review.googlesource.com/c/sdk/+/152802
1 file changed
tree: b40ee1cc7c3eb164ab2098975c4a3722b06e363b
  1. .github/
  2. assets/
  3. benchmarking/
  4. build/
  5. ci/
  6. common/
  7. docs/
  8. examples/
  9. flow/
  10. flutter_frontend_server/
  11. fml/
  12. lib/
  13. runtime/
  14. shell/
  15. sky/
  16. testing/
  17. third_party/
  18. tools/
  19. vulkan/
  20. web_sdk/
  21. .ci.yaml
  22. .cirrus.yml
  23. .clang-format
  24. .clang-tidy
  25. .gitattributes
  26. .gitignore
  27. analysis_options.yaml
  28. AUTHORS
  29. BUILD.gn
  30. CONTRIBUTING.md
  31. DEPS
  32. Doxyfile
  33. LICENSE
  34. README.md
README.md

Flutter Engine

Build Status - Cirrus

Flutter is Google's SDK for crafting beautiful, fast user experiences for mobile, web, and desktop from a single codebase. Flutter works with existing code, is used by developers and organizations around the world, and is free and open source.

The Flutter Engine is a portable runtime for hosting Flutter applications. It implements Flutter's core libraries, including animation and graphics, file and network I/O, accessibility support, plugin architecture, and a Dart runtime and compile toolchain. Most developers will interact with Flutter via the Flutter Framework, which provides a modern, reactive framework, and a rich set of platform, layout and foundation widgets.

If you want to run/contribute to Flutter Web engine, more tooling can be found at felt. This is a tool written to make web engine development experience easy.

If you are new to Flutter, then you will find more general information on the Flutter project, including tutorials and samples, on our Web site at Flutter.dev. For specific information about Flutter's APIs, consider our API reference which can be found at the docs.flutter.dev.

Flutter is a fully open source project, and we welcome contributions. Information on how to get started can be found at our contributor guide.