[vm] Tweak location of Perfetto protos This CL tries to address version skew issues which occur in internal monorepo which we created by checking in *.pbzero.h files into runtime/vm/protos/*. These files refer to protozero internal headers, which in the internal monorepo come from a shared Perfetto dependency which does not necessarily match the version we pinned in our DEPS and used to generated these files. This version skew caused problems for the Perfetto team, see https://github.com/google/perfetto/pull/3195 To resolve this change layout of our repo to allow us to depend on the shared Perfetto entirely - including its version of *.pbzero.h headers. We change include paths in the VM source to #include "third_party/perfetto/protos/..." which match location of these headers in the internal monorepo. To make the code compile in the normal SDK checkout we shift location of Perfetto and checked in code: * Perfetto source moves from third_party/perfetto to third_party/perfetto/src. * Generated code moves from runtime/vm/protos into third_party/perfetto/protos. Note: experiments show that *.pbzero.h files tree-shake very well and you pay only for things that you use. That means depending on *.pbzero.h files generated from full message definitions rather than our manually tree-shaken versions does not actually increase the size of the VM binaries. We could switch our external build to do the same but this would make protoc a build time dependency, which seems excessive. TEST=ci Change-Id: I724b9d9304be83302a5d83c2337154b36a6a6964 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/454260 Commit-Queue: Slava Egorov <vegorov@google.com> Reviewed-by: Ben Konyi <bkonyi@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.