Roll BoringSSL from 706742e482d8 to eae76e0715de (28 revisions) https://boringssl.googlesource.com/boringssl.git/+log/706742e482d8..eae76e0715de 2025-10-10 davidben@google.com Test bssl::InplaceVector with a move-only type 2025-10-10 drysdale@google.com Rust wrappers for external mu variant of ML-DSA 2025-10-10 davidben@google.com Document that ASN1_STRING_set_by_NID enforces the bounds on the string 2025-10-10 davidben@google.com Also accept incorrectly-encoded X509 v1 version fields again 2025-10-09 mpolzer@google.com Prevent false positive in constant time checks 2025-10-09 chlily@google.com Allow empty extension lists in X.509 2025-10-08 davidben@google.com Use a less verbose pattern to heap-allocate temporaries in ML-DSA 2025-10-08 davidben@google.com Const-correct the internal/external pointer casts 2025-10-08 davidben@google.com Don't have separate BCM and ML-KEM and ML-DSA types 2025-10-08 davidben@google.com Unwind <openssl/bcm_public.h> 2025-10-07 kwlyeo@google.com Add SSWU_NU encode-to-curve functions from RFC 9380. 2025-10-07 agl@chromium.org Unify the HPKE implementation for ML-KEM. 2025-10-07 davidben@google.com Update Go on CI 2025-10-07 davidben@google.com Bump the macOS versions on our CI to macOS 12 or 13 2025-10-07 davidben@google.com Deprecate SSL_CIPHER_get_name 2025-10-07 davidben@google.com Remove some unused constants 2025-10-07 davidben@google.com Order TLS1_TXT_* and TLS1_CK_* in the same order 2025-10-07 davidben@google.com Remove TLS1_TXT_* constants for unimplemented cipher suites 2025-10-07 davidben@google.com Add OIDs and NIDs for ML-DSA-{44,65,87} and ML-KEM-{768,1024} 2025-10-06 davidben@google.com Restore TLS 1.3 TLS1_CK_* constants 2025-10-06 davidben@google.com Remove TLS1_CK_* constants for unimplemented cipher suites 2025-10-06 poliudian-iv@yandex-team.ru Add additional check, as contract of function 2025-10-03 chlily@google.com Bump BORINGSSL_API_VERSION to 37 2025-10-02 chlily@google.com Add API for caller to hint server's preferred key shares 2025-10-02 davidben@google.com Update CI dependencies 2025-10-02 davidben@google.com Update Bazel deps and bump version for BCR 2025-10-02 agl@imperialviolet.org Add newer HPKE configuration to Rust wrappers. 2025-10-02 davidben@google.com Rework ML-DSA modular operations 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: I8bd81225791db7c2f7f038c0a7f917edcab5d758 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/454403 Reviewed-by: Alexander Aprelev <aam@google.com> Commit-Queue: Alexander Aprelev <aam@google.com> Reviewed-by: Brian Quinlan <bquinlan@google.com> https://dart.googlesource.com/sdk/+/e4175c667b7bd5a8bf98cb05cba7f810e19856e7
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.