firka/flutter
firka/flutter
4
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
flutter/bin/internal
History
engine-flutter-autoroll f329b4623a Roll engine 10eb972fc15b..319e1c5c1d1c (4 commits) (#26936) 
* 88fee0804 Remove the shell build target's dependency on the embedder library (flutter/engine#7549)

* 2123d3a56 Keep engine alive if VC is not deallocated (flutter/engine#7544)

* c57e66fda fixes android pressure range (flutter/engine#7516)

* 319e1c5c1 Roll src/third_party/skia 347d36586cb6..325778b8884b (7 commits) (flutter/engine#7552)
2019-01-22 20:25:13 -08:00
..
engine.merge_method
Switch engine.merge_method back to squash (#24319)
2018-11-13 17:12:36 -08:00
engine.version
Roll engine 10eb972fc15b..319e1c5c1d1c (4 commits) (#26936)
2019-01-22 20:25:13 -08:00
goldens.version
Roll engine to 10eb972fc15b8a3f97ed7c26032cae03b10fca2c (#26926)
2019-01-22 18:26:17 -08:00
gradle_wrapper.version
Make artifacts URLs configurable. (#13380)
2017-12-07 16:30:23 +01:00
material_fonts.version
Make artifacts URLs configurable. (#13380)
2017-12-07 16:30:23 +01:00
README.md
Add engine merge method configuration (#23953)
2018-11-07 13:06:38 -08:00
update_dart_sdk.ps1
update_dart_sdk.ps1: Fall back to Invoke-WebRequest if BITS fails (#19873)
2018-07-27 14:29:20 -07:00
update_dart_sdk.sh
Update links for China help (#25238)
2018-12-21 10:12:49 -08:00

README.md

Dart SDK dependency

The bin/internal/engine.version file controls which version of the Flutter engine to use. The file contains the commit hash of a commit in the https://github.com/flutter/engine repository. That hash must have successfully been compiled on https://build.chromium.org/p/client.flutter/ and had its artifacts (the binaries that run on Android and iOS, the compiler, etc) successfully uploaded to Google Cloud Storage.

The /bin/internal/engine.merge_method file controls how we merge a pull request created by the engine auto-roller. If it's squash, there's only one commit for a pull request no matter how many engine commits there are inside that pull request. If it's rebase, the number of commits in the framework is equal to the number of engine commits in the pull request. The latter method makes it easier to detect regressions but costs more test resources.