| OLD | NEW |
|---|
| 1 This directory contains the hashes of tar.gz files uploaded to cloud storage. | 1 This directory contains the hashes of tar.gz files uploaded to cloud storage. |
| 2 Hooks in the DEPS files run "download_from_google_storage" to download these | 2 Hooks in the DEPS files run "download_from_google_storage" to download these |
| 3 tarfiles, and unpack them. These tar files contain a stable Dart SDK, which | 3 tarfiles, and unpack them. These tar files contain a stable Dart SDK, which |
| 4 is used to build the observatory and to run the test scripts. | 4 is used to build the observatory and to run the test scripts. |
| 5 | 5 |
| 6 The hooks use the --auto-platform feature, so that only the SDK for the | 6 The hooks use the --auto-platform feature, so that only the SDK for the |
| 7 current platform (linux, macos, or windows) is downloaded. This requires | 7 current platform (linux, macos, or windows) is downloaded. This requires |
| 8 the subdirectories to have the special names "linux", "win", and "mac", which | 8 the subdirectories to have the special names "linux", "win", and "mac", which |
| 9 the download script is hardcoded to recognize. | 9 the download script is hardcoded to recognize. |
| 10 | 10 |
| 11 The linux SDK has two extra dart executables added to the bin directory. | 11 The linux SDK has two extra dart executables added to the bin directory. |
| 12 'dart-arm' and 'dart-arm64' are executables compiled to run on | 12 'dart-arm' and 'dart-arm64' are executables compiled to run on |
| 13 arm and arm64 (aarch64) processors, respectively. We are currently | 13 arm and arm64 (aarch64) processors, respectively. We are currently |
| 14 using the 32-bit ia32 build as the default on linux, windows, and macos. | 14 using the 32-bit ia32 build as the default on linux, windows, and macos. |
| 15 If we switch to the 64-bit build on linux, the snapshots will no longer be | 15 If we switch to the 64-bit build on linux, the snapshots will no longer be |
| 16 portable to arm and arm64, and we will need to upload complete SDKs for each | 16 portable to arm and arm64, and we will need to upload complete SDKs for each |
| 17 processor architecture. | 17 processor architecture. |
| 18 | 18 |
| 19 To upload new versions of these tar files, use the "upload_to_google_storage" | 19 To upload new versions of these tar files, use the "upload_to_google_storage" |
| 20 tool in depot_tools, and download the new stable SDKs from the dartlang.org | 20 tool in depot_tools, and download the new stable SDKs from the dartlang.org |
| 21 web page. The mips and arm executables must be copied from the machines that | 21 web page. The arm executables must be copied from the machines that |
| 22 build them, and stripped. Because these SDKs are used for the presubmit | 22 build them, and stripped. Because these SDKs are used for the presubmit |
| 23 dartfmt check on changed files, they may need to be updated often when | 23 dartfmt check on changed files, they may need to be updated often when |
| 24 dartfmt is changing rapidly. | 24 dartfmt is changing rapidly. |
| 25 | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2858623002:
Remove MIPS support (Closed)
