| commit | 2bc4081118d07b2c49fd499100c9e942b1087c0a | [log] [tgz] |
|---|---|---|
| author | Daco Harkes <dacoharkes@google.com> | Fri Jun 13 08:04:34 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 13 08:04:34 2025 -0700 |
| tree | 06004c6f6fb0739fdde84c059496cf32a884190f | |
| parent | 5e3c017d056d4f01f4218c031fa24b5032c75af9 [diff] |
[dartdev] `dart build cli` (Removes `dart build`)
This PR changes `dart build` to have subcommands, so that we can
have different bundle formats in the future.
Moreover, it changes the following:
* `exe` to `cli`. This mirrors `dart create --template cli`
* The output executable no longer has `.exe` on MacOS and Linux.
* The output bundle now contains a `bin/` dir with the executable.
* It removes the `--target-os` option, it would simply error on
cross compilation. (And we don't want API parity with `dart
compile exe`.)
* The default output directory is somewhere in `build/`. This aligns
the behavior with Flutter. (`dart compile` puts the file next to
the Dart file, which is a source directory.)
The executables and dylibs are signed with the ad hoc code signing
`"-"`. Users will need to resign in order to distribute.
New CLI interface:
```
$ dart build cli --help
Build a Dart application for the command line.
The CLI app bundle is structured in the following manner:
bundle/
bin/
<executable>
lib/
<dynamic libraries>
Usage: dart build cli [arguments]
-h, --help Print this usage information.
-o, --output=<path> Write the output to <output>/bundle/.
This can be an absolute or relative path.
(defaults to "build/cli/macos-arm64/")
-t, --target=<path> The main entry-point file of the command-line application.
Must be a Dart file in the bin/ directory.
If the "--target" option is omitted, and there is a single Dart file in bin/,
then that is used instead.
(defaults to "bin/native_add_app.dart")
--verbosity=<level> Sets the verbosity level of the compilation.
[error] Show only error messages
[warning] Show only error and warning messages
[info] Show error, warning, and info messages
[all] (default) Show all messages
```
This PR removes support for `dart build -f exe <target>`, as
`package:args` does not support having subcommands and not
having subcommands: `Could not find a subcommand named
"bin/native_add_app.dart" for "dart build".`
Bug: https://github.com/dart-lang/sdk/issues/60730
Change-Id: I2b527754f3186ec6d0809d7ac45e05984d5c0a02
Cq-Include-Trybots: luci.dart.try:pkg-linux-debug-try,pkg-linux-release-arm64-try,pkg-linux-release-try,pkg-mac-release-arm64-try,pkg-win-release-arm64-try,pkg-mac-release-try,pkg-win-release-try
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/433160
Reviewed-by: Michael Goderbauer <goderbauer@google.com>
Reviewed-by: Ben Konyi <bkonyi@google.com>
Commit-Queue: Daco Harkes <dacoharkes@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.