languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-05 00:13:50 +00:00
Code Issues Packages Projects Releases Wiki Activity
dart-sdk/tools/3xhead_flutter_hooks.sh

26 lines
903 B
Bash
Raw Normal View History

[infra] Extend 3head patching to apply patches for flutter/flutter depending on pinned engine commit This also adds a patch to flutter/flutter to fix head-head-head configuration (until engine is rolled into framework again). Change-Id: I6dae0983126a6664337834d3c93f1369139f1ac1 Reviewed-on: https://dart-review.googlesource.com/c/91922 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Jonas Termansen <sortie@google.com>
2019-02-04 12:37:10 +00:00
#!/usr/bin/env bash
Support incompatible Dart SDK changes with patches to the Flutter Engine. The Dart SDK may change incompatibly and require a corresponding update to the Flutter Engine when Flutter Enginer rolls its Dart SDK. The flutter targets on Golem uses a 3-way HEAD of the Dart SDK, the Flutter Engine, and the Flutter Framework, meaning that it needs to apply the corresponding update to the Flutter Engine immediately. Otherwise the Flutter targets will be broken and not successfully run benchmarks until the next Flutter roll. This change lets the Dart SDK make incompatible changes that affects the Flutter Engine by checking in the corresponding patch into the Dart SDK along with the incompatible change. The build step will determine what the latest roll is by looking up which Dart SDK Hash the Flutter Engine has pinned. If a patch exists for that hash, then that patch is applied to the Flutter Engine. For instance, if the Flutter Engine commit ab12 has pinned the Dart SDK commit cd34, then it the patch tools/patches/flutter-engine/cd34.patch is applied. Once the Flutter Engine rolls its Dart Engine, usually by applying an equivalent patch, the roll commit will start refering to an non-existent patch and the HEADs will be built together pristine again. Finally cd32.patch can be removed from new versions of the Dart SDK. The tools/patches/flutter-engine/apply.sh script is applies such patches in 3-way HEAD builds. The create.sh script is meant to be used by developers when making incompatible changes to the Dart SDK that affects the Flutter Engine. The top level tools/3xhead_flutter_hooks.sh script is meant to be used by the CI as forward compatibility if additional hooks are added in the future. Change-Id: Ibf8e125b26dac319ba1c5302c003d7668155336a Reviewed-on: https://dart-review.googlesource.com/64684 Reviewed-by: Martin Kustermann <kustermann@google.com>
2018-07-12 15:47:16 +00:00
#
# Copyright (c) 2018, the Dart project authors. Please see the AUTHORS file
# for details. All rights reserved. Use of this source code is governed by a
# BSD-style license that can be found in the LICENSE file.
#
# After you have checked out a flutter engine with the latest framework and the
# latest dart sdk, run this script to apply workarounds to the source code. It
# may patch up the source code so the three HEADs work together correctly.
#
# Usage: src/third_party/dart/tools/3xhead_flutter_hooks.sh
# (run inside the root of a flutter engine checkout)
set -e
[infra] Extend 3head patching to apply patches for flutter/flutter depending on pinned engine commit This also adds a patch to flutter/flutter to fix head-head-head configuration (until engine is rolled into framework again). Change-Id: I6dae0983126a6664337834d3c93f1369139f1ac1 Reviewed-on: https://dart-review.googlesource.com/c/91922 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Jonas Termansen <sortie@google.com>
2019-02-04 12:37:10 +00:00
DIR=$(dirname -- "$(which -- "$0")")
. $DIR/patches/utils.sh
ensure_in_checkout_root
# Apply patches to the Flutter Framework if needed.
src/third_party/dart/tools/patches/flutter-flutter/apply.sh
Support incompatible Dart SDK changes with patches to the Flutter Engine. The Dart SDK may change incompatibly and require a corresponding update to the Flutter Engine when Flutter Enginer rolls its Dart SDK. The flutter targets on Golem uses a 3-way HEAD of the Dart SDK, the Flutter Engine, and the Flutter Framework, meaning that it needs to apply the corresponding update to the Flutter Engine immediately. Otherwise the Flutter targets will be broken and not successfully run benchmarks until the next Flutter roll. This change lets the Dart SDK make incompatible changes that affects the Flutter Engine by checking in the corresponding patch into the Dart SDK along with the incompatible change. The build step will determine what the latest roll is by looking up which Dart SDK Hash the Flutter Engine has pinned. If a patch exists for that hash, then that patch is applied to the Flutter Engine. For instance, if the Flutter Engine commit ab12 has pinned the Dart SDK commit cd34, then it the patch tools/patches/flutter-engine/cd34.patch is applied. Once the Flutter Engine rolls its Dart Engine, usually by applying an equivalent patch, the roll commit will start refering to an non-existent patch and the HEADs will be built together pristine again. Finally cd32.patch can be removed from new versions of the Dart SDK. The tools/patches/flutter-engine/apply.sh script is applies such patches in 3-way HEAD builds. The create.sh script is meant to be used by developers when making incompatible changes to the Dart SDK that affects the Flutter Engine. The top level tools/3xhead_flutter_hooks.sh script is meant to be used by the CI as forward compatibility if additional hooks are added in the future. Change-Id: Ibf8e125b26dac319ba1c5302c003d7668155336a Reviewed-on: https://dart-review.googlesource.com/64684 Reviewed-by: Martin Kustermann <kustermann@google.com>
2018-07-12 15:47:16 +00:00
# Apply patches to the Flutter Engine if needed.
src/third_party/dart/tools/patches/flutter-engine/apply.sh
Reference in a new issue Copy permalink