| commit | 5c1796f4e0fd2aa3eea51e65259bd0c231d4c5ce | [log] [tgz] |
|---|---|---|
| author | Gabriel Terwesten <gabriel@terwesten.net> | Tue Jan 07 08:15:39 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 07 08:15:39 2025 -0800 |
| tree | d5df8bae22bacffb495b77fc144474a392f98b20 | |
| parent | 1830689c808a5876cb52718b13a953495af3bc33 [diff] |
[vm,ffi] Avoid linking test DLLs to `dart.exe` The `ffi_test_functions` shared library needs to access functions from `dart_api.h` and `dart_native_api.h`, which are only available in the Dart executable. UNIX shared libraries can have undefined symbols, which are resolved at runtime and can be found in the loading executable. Windows DLLs cannot have undefined symbols, but they can be dynamically linked to an executable (in this case `dart.exe`). This requires the DLL to be able to find the executable at runtime. A better solution is to include implementations for the Dart APIs in the DLL itself, that use `GetModuleHandle(NULL)` to get a handle to the executable and `GetProcAddress` to get the address of the function. This is what `dart_api_win.c` does. Fixes https://github.com/dart-lang/sdk/issues/40579 Fixes https://github.com/dart-lang/sdk/issues/59677 TEST=ci Cq-Include-Trybots: luci.dart.try:vm-win-release-ia32-try,vm-win-debug-x64c-try,vm-win-debug-x64-try,vm-win-debug-arm64-try,vm-msvc-windows-try,vm-aot-win-debug-x64c-try,vm-aot-win-debug-x64-try,vm-aot-win-debug-arm64-try,vm-aot-win-product-x64-try,vm-aot-win-release-x64-try,vm-aot-win-release-arm64-try,pkg-win-release-try,pkg-win-release-arm64-try,dart-sdk-win-try,dart-sdk-win-arm64-try Change-Id: I7f971a8ce21e03d18ed2967e74998f925c9236b2 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/400582 Commit-Queue: Daco Harkes <dacoharkes@google.com> Reviewed-by: Daco Harkes <dacoharkes@google.com> Reviewed-by: Alexander Thomas <athom@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.