[front_end] Pass all diagnostic arguments to Message.arguments prior to conversion. Previously, most entries in the `Message.arguments` map directly reflected the values passed to `withArgumentsOld` (prior to converting and the arguments into a form more suitable for display), but there were some exceptions: - For `name`, `name2`, `name3`, and `name4` parameters, the entry in `Message.arguments` was the value of the name after passing it through the function `demangleMixinApplicationName`. - For `nameOKEmpty`, the entry in `Message.arguments` was the value of the name after substituting `(unnamed)` for the empty string. - For `stringOKEmpty`, the entry in `Message.arguments` was the value of the name after substituting `(empty)` for the empty string. This CL changes the generated `withArgumentsOld` functions so that all the values in `Message.arguments` uniformly directly reflect the values passed to `withArgumentsOld`. In practice this has no user-visible effect, because the only use of `Message.arguments` outside of testing is to convert parser diagnostics to analyzer form, and none of the above conversions have any effect on parser diagnostics. (This is because (a) mixin name mangling happens after the parsing stage, and (b) the parser diagnostics don't use `nameOKEmpty` or `stringOKEmpty` parameters.) In follow-up CLs, I plan to rework the code generator for `withArgumentsOld` so that it's easy to generate a parallel `withArguments` function that takes named arguments. Starting from a more uniform behavior will make that rework easier. Change-Id: I6a6a69642e1d9b8277c4959d4a9c2d5ae0cd5b8f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/447627 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Paul Berry <paulberry@google.com> https://dart.googlesource.com/sdk/+/4e9b0cd6de51fff91291f5afb02e5a3240e245b3
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.