| commit | 9a6503b5006b34eb5645f952f4b3e08dd8641f97 | [log] [tgz] |
|---|---|---|
| author | Daco Harkes <dacoharkes@google.com> | Fri Oct 04 14:17:21 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 04 14:17:21 2024 +0000 |
| tree | f41a6e5d294b9bb0c18c23171094de9d61664124 | |
| parent | 57bec7feddc43c4e9486697e8db960434f7a8aa7 [diff] |
[vm/ffi] Add embedder API for resolving asset ids Extends the `NativeAssetsApi` with a `dlopen` that takes an asset id instead of an asset path. This enables the embedder (instead of the vm) to resolve the asset id to asset path. Additionally, the `NativeAssetsApi` gets an `available_assets` callback to report which asset ids are available if asset resolution failed. (Otherwise, users would lose this important part of the error message on failed resolution.) We postpone migrating the Dart standalone embedder to this API: https://dart-review.googlesource.com/c/sdk/+/388160. That CL verifies this new API and it's implementation. Without that CL this new API is hard to test. So, no further tests are added here. Tests that verify the old behavior for the standalone embedder: TEST=tests/ffi/native_assets/* TEST=pkg/dartdev/test/native_assets/* Bug: https://github.com/flutter/flutter/issues/154425 Change-Id: I04d0fb45dc5663e63d91b21a6f5764929f10aaff Cq-Include-Trybots: dart/try:vm-aot-linux-debug-x64-try,vm-aot-linux-debug-x64c-try,vm-aot-mac-release-arm64-try,vm-aot-mac-release-x64-try,vm-aot-obfuscate-linux-release-x64-try,vm-aot-optimization-level-linux-release-x64-try,vm-aot-win-debug-arm64-try,vm-aot-win-debug-x64-try,vm-aot-win-debug-x64c-try,pkg-linux-debug-try,pkg-linux-release-arm64-try,pkg-mac-release-try,pkg-mac-release-arm64-try,pkg-win-release-try,pkg-win-release-arm64-try,vm-aot-asan-linux-release-x64-try,vm-asan-linux-release-x64-try,vm-aot-msan-linux-release-x64-try,vm-msan-linux-release-x64-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/388161 Commit-Queue: Daco Harkes <dacoharkes@google.com> Reviewed-by: Martin Kustermann <kustermann@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.