Ömer Ağacan
f242e0f6c4
The update script at
`third_party/perfetto/tools/compile_perfetto_protos.dart` doesn't work
out of the box. Steps to to generate this CL:
- Apply diffs:
```
diff --git a/DEPS b/DEPS
index c7b224d28c2..6532cf91e8c 100644
--- a/DEPS
+++ b/DEPS
@@ -75,7 +75,7 @@ vars = {
"jsc_tag": "version:301576",
# https://chrome-infra-packages.appspot.com/p/fuchsia/third_party/clang
- "clang_version": "git_revision:8b93f27cf7e6e53636db870873b53269efa3cca4",
+ "clang_version": "git_revision:49f39b349db181ca516eb0253462105ff0e2c634",
# https://chrome-infra-packages.appspot.com/p/gn/gn
"gn_version": "git_revision:07d3c6f4dc290fae5ca6152ebcb37d6815c411ab",
```
```
diff --git a/build/config/compiler/BUILD.gn b/build/config/compiler/BUILD.gn
index b041a075b5e..077dd104d79 100644
--- a/build/config/compiler/BUILD.gn
+++ b/build/config/compiler/BUILD.gn
@@ -651,6 +651,7 @@ if (is_win) {
"-Wno-tautological-constant-compare",
"-Wno-unused-but-set-variable", # icu
"-Wno-deprecated-non-prototype", # zlib
+ "-Wno-unnecessary-virtual-specifier",
]
} else {
default_warning_flags += [
```
This will make the perfetto build targets buildable.
- Remove all generated proto files in `pkg/vm_service_protos`.
`compile_perfetto_protos.dart` doesn't properly update existing files,
and doesn't delete files that are not generated by the protoc plugin.
- Run `third_party/perfetto/tools/compile_perfetto_protos.dart` with the
in-tree SDK.
- `git cl format .` to format generated files.
Also update transformer test expectations based on the new plugin and
the lib.
Tested: existing tests
Change-Id: I475f12313687b93b8f0ed01206cc7a9fcb2725e1
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/459421
Reviewed-by: Slava Egorov <vegorov@google.com>
Commit-Queue: Ömer Ağacan <omersa@google.com>
Dart
An approachable, portable, and productive language for high-quality apps on any platform
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).
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 in our repo at docs.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Roadmap
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.