| commit | e0b08fadd81be7e227057872c75e728ff8c90a64 | [log] [tgz] |
|---|---|---|
| author | Jonas Termansen <sortie@google.com> | Fri Apr 12 22:06:32 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 12 22:06:32 2024 +0000 |
| tree | c6aeddc68b5c962a3571a2b8dcc5e4b9b34f8d87 | |
| parent | 8e275a4c6d7833d7c61a9a2f118fcb3d0e86c662 [diff] |
Reland "[infra] RBE all the things." This is a reland of commit b3253d9c8b2436060096234b69860caac67efbac Fix the gn rules so the RBE offloading only happens in the Dart build and the conflicting RBE configuration is not included otherwise. This ensures this change can roll into Flutter while we design a better solution to compose the projects' RBE usages. Original change's description: > [infra] RBE all the things. > > This change offloads all Dart actions during the build to RBE using > the new rewrapper_dart.py script that understands all the different > command line invocations of Dart programs and translates it into the > appropriate rewrapper invocation, with a full list of input and output > files and no absolute paths. > > The dart actions are all considered to be expensive RBE compilation > steps that may be much slower on RBE than locally due to the low > parallelism of the build during these stages and the comperatively > slower bots in the RBE pools. The build uses the racing strategy by > default for these compilations, such that cache hits are still used > if available, and otherwise a local build is transparently used if it > happens to be faster. The bots will use the remote strategy by default > unlike developers, such that the rewrapper_dart.py script does not fail. > > rewrapper_dart.py contains a tiny dart import proprocessor written > in python and a big argument parser that understands every command > invoked during the build and the semantic meaning of every option. > > The absolute paths used during the Dart SDK build is not solved in > this changelist, which just works around them initially, but these > will be fixed in follow up changes with the appropriate teams now > that this change proves they are not needed. > > Bug: b/333595242 > Change-Id: I36603ec1bf16f4ac87d56635cc1c98e8686a4028 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/335827 > Reviewed-by: William Hesse <whesse@google.com> > Commit-Queue: Jonas Termansen <sortie@google.com> Bug: b/333595242 Change-Id: I43bec2e7fcad375e972ca447aa13ae65b0ce09ae Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/362661 Reviewed-by: William Hesse <whesse@google.com> Commit-Queue: Jonas Termansen <sortie@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 on our wiki.
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.