John Messerly
6c7cd9b731
Moves: test/sdk --> tool/input_sdk_src Also moves: test/sdk/lib/_internal/js_lib --> tool/input_sdk_patch we'll eventually need to customize that code Adds tool/patch_sdk.dart, an offline transformation step that produces: test/generated_sdk Essentially this merges the "external" declarations and the @patch syntactically. There's a comment in tool/patch_sdk.dart explaining the rationale behind this approach. There's still *lots* to do in the generated code. This does none of that. The only new code is tool/patch_sdk.dart and the minimum changes to test/codegen_test.dart and js_codegen.dart to get test.sh running and debuggable. Tracking bug for SDK is https://github.com/dart-lang/dart-dev-compiler/issues/58 R=sigmund@google.com, vsm@google.com Review URL: https://chromereviews.googleplex.com/157137013
27 lines
737 B
Markdown
27 lines
737 B
Markdown
## Tools for processing the Dart SDK
|
|
|
|
# patch_sdk.dart
|
|
|
|
This script combines:
|
|
|
|
tool/input_sdk_src/...
|
|
tool/input_sdk_patch/...
|
|
|
|
and produces the merged SDK sources in:
|
|
|
|
test/generated_sdk/...
|
|
|
|
The result has all "external" keywords replaced with the @patch implementations.
|
|
|
|
Generally local edits should be to `input_sdk_patch`, as it is specific to DDC.
|
|
`input_sdk_src` should represent unmodified SDK sources to the maximum extent
|
|
possible. Currently there are slight edits to the type annotations in some
|
|
cases.
|
|
|
|
See patch_sdk.dart for more information.
|
|
|
|
# sdk_version_check.dart
|
|
|
|
Asserts that the Dart VM is at least a particular semantic version.
|
|
It returns an exit code to make it easy to integrate with shell scripts.
|