DEV/flutter_flutter
1
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2026-02-20 02:29:02 +08:00
Code Issues Packages Projects Releases Wiki Activity
flutter_flutter/frontend_server
History
Ben Konyi 45664a6aac
Roll src/third_party/dart b11308657c..b11308657c (0 commits) (#9037) 
* Roll src/third_party/dart b48c8b1d1c..433bc1b350 (2 commits)

433bc1b350 [vm/compiler] Avoid adding unused Redefinition instructions
04e329b6ed Add override annotations across DDC

* Roll src/third_party/dart 433bc1b350..6d76c8790d (5 commits)

6d76c8790d bump to linter 0.1.89
0799ac0edb Enforce DDC lints
2fd1021326 [dartdevc] Turn on lints and cleanup violations
9adc5be551 Dartfmt all of DDC with the latest
e9b5c9ce8b Ignore todos in DDC

* Remove duplicate flag "track-widget-creation". Unblocks SDK roll.

* Roll src/third_party/dart b11308657c..b11308657c (0 commits)
2019-05-21 16:32:50 -07:00
..
bin
Roll Dart to version be6309690fd60284a87f3258a740c7c30efb1092 (#5987)
2018-08-10 13:42:44 +02:00
lib
Roll src/third_party/dart b11308657c..b11308657c (0 commits) (#9037)
2019-05-21 16:32:50 -07:00
test
new lints (#8849)
2019-05-07 16:10:21 -07:00
.gitignore
Analysis cleanup of the Dart in the Engine repo (#4554)
2018-01-17 09:48:56 -08:00
BUILD.gn
GN Format all files in the engine. (#8369)
2019-03-29 12:44:57 -07:00
pubspec.yaml
Generate frontend server's .packages from Dart .packages file instead of using pub get. (#5360)
2018-05-24 18:33:52 +02:00
README.md
Introduce frontend_server that flutter tools will use for compilation. (#3982)
2017-08-21 12:55:17 -07:00

README.md

Frontend Server

Frontend server is simple wrapper around Dart Frontend. It is a Dart application that compiles Dart source into Dart Kernel binary (.dill-file). Documentation on Dart Kernel (semantic, binary format, etc) can be found here: https://github.com/dart-lang/sdk/wiki/Kernel-Documentation.

Frontend server runs in two modes:

  • immediate mode, where Dart source file name is provided as command line argument;
  • interactive mode, where communication is happening over stdin/stdout.

Interactive mode instructions

Compile/Recompile

compile <input.dart>

Compiles <input.dart> Dart source file with Dart Frontend. Replies with result response.

recompile <boundary-key>
<path/to/updated/file1.dart>
<path/to/updated/file2.dart>
...
<boundary-key>

Incrementally recompiles Dart program previously compiled in current session, taking into account changes in the listed files. Replies with result response.

Relative paths should be relative to current working directory for the shell that launched Frontend Server.

Accept/Reject

accept

Accepts results of incremental compilation, so that on next recompilation request Dart Frontend will not include these recompiled files.

reject

Rejects results of incremental compilation, so that on next recompilation request Dart Frontend will include compilation results from previously rejected recompilation in addition to what it will recompile based on newly changed files. Small technical detail is that Dart Frontend will not recompile files from previously rejected recompilation attempts (unless they were changed since then), it will just include appropriate kernel binaries it kept around from those previously rejected compilation requests.

One use of accept and reject instructions is in the context of Dart VM hot-reload. Dart VM can reject user-provided incremental change to what is currently running. It could happen for variety of Dart VM internal reasons. For example, if incremental update changes some class to enum, such update can not be hot-reloaded by VM at this point, will be rejected.

Quit

quit

Stops the server.

Response from the server

result <boundary-key>
<compiler output>
<boundary-key> [<output.dill>]

Response from the Dart Frontend compiler is bracketed by <boundary-key> tags. If the compiler was able to produce a Dart Kernel file, the name of this file <output.dill> is provided too. If the compiler encountered unrecoverable errors, there will be no output file name provided.