These tasks create self-contained archives containing the Dart VM and snapshots
of the package's executables, which can then be easily distributed. They're the
basis for many other tasks that upload the packages to various package managers.
They're enabled by calling pkg.addStandaloneTasks().
Standalone executables are built and executed in a context with the version
environment declaration set to the package's version. This can be accessed with
String.fromEnvironment().
Uses configuration: pkg.executables, pkg.version
Output: build/$executable.snapshot
Compiles each executable in the package to a kernel snapshot with asserts disabled.
Uses configuration: pkg.executables, pkg.version
Output: build/$executable.snapshot
Compiles each executable in the package to a kernel snapshot with asserts enabled.
Uses configuration: pkg.executables, pkg.version
Output: build/$executable.native
Compiles each executable in the package to a native code snapshot (what Dart calls an "AOT Application snapshot"). This is unavailable on 32-bit host systems.
Defines an environment constant named version set to pkg.version that
can be accessed from within each entrypoint via String.fromEnvironment().
Depends on: pkg-compile-snapshot-dev
Uses configuration: pkg.executables, pkg.version
Output: build/$executable (on Linux and Mac OS) or build/$executable.bat (on
Windows)
Creates scripts for each of this package's executables that executes them with
asserts enabled. The details of how the executables are compiled may change over
time or from platform to platform for increased efficiency, but they'll always
be invoked through the same scripts and testing APIs such as pkg.start(),
pkg.executableRunner(), and pkg.executableArgs() will always work
with them.
Note: We recommend that you use the testing APIs rather than invoking the wrapper scripts from your test code. Killing a batch script on Windows won't kill its child process, which can cause unexpected errors when testing.
Depends on: pkg-compile-snapshot or pkg-compile-native
Uses configuration: pkg.version, pkg.standaloneName, pkg.executables
Output: build/$standaloneName-$version-$os-$arch.(tar.gz|zip)
Creates an archive that contains all this package's entrypoints along with the Dart VM for the given operating system and architecture, with top-level scripts that can be used to invoke them.
Any OS's packages can be built regardless of the OS running the task, but if the host OS matches the target OS and the architecture is 64-bit, executables will be built as native ("AOT") executables, which are substantially faster and smaller than the kernel snapshots that are generated otherwise.
This produces a ZIP file in Windows, and a gzipped TAR file on Linux and Mac OS.
Note that pkg-standalone-macos-ia32 doesn't exist. The Dart SDK no longer has
a 32-bit distribution for Mac OS (as of Dart 2.7), because Mac OS Catalina and
later are 64-bit-only. Similarly, pkg-standalone-windows-arm64 doesn't exist
because the Dart SDK has never had an ARM distribution for Windows.
A utility task for creating a packages for all operating systems in the same step.