Roll BoringSSL from a70ec8dd2cc1 to 45cab558a838 (19 revisions) https://boringssl.googlesource.com/boringssl.git/+log/a70ec8dd2cc1..45cab558a838 2025-05-09 davidben@google.com Send only usable trust anchor IDs in EncryptedExtensions 2025-05-09 davidben@google.com Add CBB_discard 2025-05-08 davidben@google.com Document that "add1" is like "set1" 2025-05-08 davidben@google.com Remove ext_dat.h 2025-05-08 davidben@google.com Remove v3_ocsp_accresp 2025-05-07 davidben@google.com Don't stack-allocate incomplete X509/X509_CRL objects 2025-05-07 davidben@google.com Also add BIO_meth_get_write and BIO_meth_get_read 2025-05-07 davidben@google.com Reapply "Remove Karatsuba multiplication in BIGNUM" 2025-05-07 davidben@google.com Test non-NEON codepaths with a OPENSSL_NO_STATIC_NEON_FOR_TESTING 2025-05-07 davidben@google.com Simplify the implementation of OPENSSL_STATIC_ARMCAP 2025-05-02 davidben@google.com Use C++ destructors a little more 2025-05-02 davidben@google.com Clean up ssl_file.cc 2025-05-02 davidben@google.com Remove some dead code from SSL_CTX_use_certificate_chain_file 2025-05-02 davidben@google.com Write some tests for ssl_file.cc 2025-05-02 gavinmak@google.com Remove --no_auth from download_from_google_storage hooks 2025-05-01 davidben@google.com Rewrite crypto_md32_* with templates instead of function pointers 2025-05-01 davidben@google.com Convert EC_KEY_derive_from_secret to scopers 2025-05-01 davidben@google.com Add various missing includes 2025-04-30 davidben@google.com delocate: Support more aarch64 load instructions with :lo12: If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/boringssl-dart-sdk Please CC dart-engprod@google.com,dart-vm-gardener@grotations.appspotmail.com,dart-vm-team@google.com on the revert to ensure that a human is aware of the problem. To file a bug in BoringSSL: https://crbug.com/boringssl/new To file a bug in Dart SDK: https://github.com/dart-lang/sdk/issues To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: dart-vm-gardener@grotations.appspotmail.com Change-Id: Ie56067d5e51acfcb9107e9de5720c21a188b6dfc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/427641 Reviewed-by: Alexander Aprelev <aam@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com> Commit-Queue: Alexander Aprelev <aam@google.com> https://dart.googlesource.com/sdk/+/68e917c116e493aed74f1fda16ee715e8ec53b03
Monorepo is:
With depot_tools installed and on your path, create a directory for your monorepo checkout and run these commands to create a gclient solution in that directory:
mkdir monorepo cd monorepo gclient config --unmanaged https://dart.googlesource.com/monorepo gclient sync -D
This gives you a checkout in the monorepo directory that contains:
monorepo/ DEPS - the DEPS used for this gclient checkout commits.json - the pinned commits for Dart, flutter/engine, and flutter/flutter tools/ - scripts used to create monorepo DEPS engine/src/ - the flutter/buildroot repo flutter/ - the flutter/engine repo out/ - the build directory, where Flutter engine builds are created third_party/ - Flutter dependencies checked out by DEPS dart/ - the Dart SDK checkout. third_party - Dart dependencies, also used by Flutter flutter/ - the flutter/flutter repo
Flutter's instructions for building the engine are at Compiling the engine
They can be followed closely, with a few changes:
goma_ctl ensure_start is sufficient.Example build commands that work on linux:
MONOREPO_PATH=$PWD if [[ ! $PATH =~ (^|:)$MONOREPO_PATH/flutter/bin(:|$) ]]; then PATH=$MONOREPO_PATH/flutter/bin:$PATH fi export GOMA_DIR=$(dirname $(command -v gclient))/.cipd_bin goma_ctl ensure_start pushd engine/src flutter/tools/gn --goma --no-prebuilt-dart-sdk --unoptimized --full-dart-sdk autoninja -C out/host_debug_unopt popd
The Flutter commands used to build and run apps will use the locally built Flutter engine and Dart SDK, instead of the one downloaded by the Flutter tool, if the --local-engine option is provided.
For example, to build and run the Flutter spinning square sample on the web platform,
MONOREPO_PATH=$PWD cd flutter/examples/layers flutter --local-engine=host_debug_unopt \ -d chrome run widgets/spinning_square.dart cd $MONOREPO_PATH
To build for desktop, specify the desktop platform device in flutter run as -d macos or -d linux or -d windows. You may also need to run the command
flutter create --platforms=windows,macos,linux
on existing apps, such as sample apps. New apps created with flutter create already include these support files. Details of desktop support are at Desktop Support for Flutter
Tests in the Flutter source tree can be run with the flutter test command, run in the directory of a package containing tests. For example:
MONOREPO_PATH=$PWD cd flutter/packages/flutter flutter test --local-engine=host_debug_unopt cd $MONOREPO_PATH
Please file an issue or email the dart-engprod team with any problems with or questions about using monorepo.
We will update this documentation to address them.
flutter commands may download the engine and Dart SDK files for the configured channel, even though they will be using the local engine and its SDK.gclient sync needs to be run in an administrator session, because some installed dependencies create symlinks.