413abf0d82
Such that runtime/include/internal/dart_api_dl_impl.h ends up in include/internal/dart_api_dl_impl.h in the sdk release. Long explanation: https://dart-review.googlesource.com/c/sdk/+/164320 tried to recover the folder structure but failed to do so correctly. It put runtime/include/internal/dart_api_dl_impl.h in include/runtime/dart_api_dl_impl.h rather than include/internal/dart_api_dl_impl.h. The gn copy action only supports a single `outputs` string. https://gn.googlesource.com/gn/+/HEAD/docs/reference.md#var_outputs This string can have 'placeholders'. https://gn.googlesource.com/gn/+/HEAD/docs/reference.md#placeholders The only placeholder that preserves the original folder structure, without also nesting deeply inside folders is `source_target_relative`. If `source_target_relative` inside sdk/BUILD.gn it starts including `runtime/include/` in its path. So the only way to achieve the correct copy is by doing it in runtime/include/BUILD.gn. TEST=Manual testing, we don't have tests verifying the SDK structure. Change-Id: I9d503626266edcdd8417f5cafb0f8ff9746f89f7 Cq-Include-Trybots: luci.dart.try:dart-sdk-linux-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/200866 Reviewed-by: Tess Strickland <sstrickl@google.com> Commit-Queue: Daco Harkes <dacoharkes@google.com> |
||
|---|---|---|
| .dart_tool | ||
| .github | ||
| benchmarks | ||
| build | ||
| client | ||
| docs | ||
| pkg | ||
| runtime | ||
| samples | ||
| samples-dev/swarm | ||
| samples_2 | ||
| sdk | ||
| tests | ||
| third_party | ||
| tools | ||
| utils | ||
| .clang-format | ||
| .gitattributes | ||
| .gitconfig | ||
| .gitignore | ||
| .gn | ||
| .mailmap | ||
| .packages | ||
| .style.yapf | ||
| .vpython | ||
| AUTHORS | ||
| BUILD.gn | ||
| CHANGELOG.md | ||
| codereview.settings | ||
| CONTRIBUTING.md | ||
| DEPS | ||
| LICENSE | ||
| PATENT_GRANT | ||
| PRESUBMIT.py | ||
| README.dart-sdk | ||
| README.md | ||
| sdk_args.gni | ||
| WATCHLISTS | ||
Dart
A client-optimized language for fast apps on any platform
Dart is:
-
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
-
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
-
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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).
License & patents
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Using Dart
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).
Building Dart
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 on our wiki.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.