[ddc] Fix ddx source map paths for relative output paths. If DDC is invoked with an relative output path during the Dart SDK build itself rather than an absolute path, then the build will fail with an error message that it can't calculate the relative path between the output file and the source map. The problem is that p.url.relative cannot be used with real relative filesystem paths as the current directory is assumed to be the string '.' rather than the actual directory and the algorithm cannot perform the resolution. This change blocks the RBE dart action offloading in a follow up change, which changes the Dart SDK build to only use relative paths when building on RBE, which otherwise fails in the above manner. Fixes: b/333765428 Change-Id: I5f3d984337cdd006feeb6b721f21fa17ed0d23f5 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/362189 Reviewed-by: Nicholas Shahan <nshahan@google.com> Auto-Submit: Jonas Termansen <sortie@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.