The Fuchsia artifact builder didn't allow the end user to add more
packages to build for Fuchsia. The current default is building only
the platform-specific packages; but packages like
`flutter/shell/common:shell_tests` are also defined for Fuchsia but
not compiled by default.
This change makes it less of a hassle to compile such packages.
* 1. Manual roll of Dart 6d4e7d6830...021a49e88c
dart-lang/sdk@021a49e88c Update the way to get feature set and language version.
dart-lang/sdk@d1638508c1 Migration: streamline behavior injection in migration_cli_test.dart.
2. Update ICU dependency and adjust license script to account for this
change.
* Update license tool signature.
Updates the ANGLE checkout to the latest master. Among other things, picks up fixes for errors when building under Visual Studio 2019.
Part of fix for https://github.com/flutter/flutter/issues/48831
* use clang on Windows for everything but Android
This pulls the Clang build from Chromium. We should eventually switch to use the Fuchsia toolchain when it is available.
* change the repo fetch script to recognize candidate versions such as flutter-1.17-candidate.3. Originally the script only accepted branches such as v0.7.3 as valid engine branches.
* addressing reviewer comments: changing the release regular expression
Desktop embedding dependencies can trigger gn-generation-time
requiremenets; e.g., the Linux embeddings have pkg-config dependencies.
This can be problematic in some build environments, such as building
flutter_engine.so with a custom sysroot where those higher-level
dependencies aren't available.
This flag allows generating build files that don't have those
dependencies.
- Adds an explicit option for not building the GLFW embedding.
- Disables GLFW by default on Windows, where it's no longer the
uploaded embedding.
- Moves the X11 pkg-config, which is only used by the GLFW embedding,
behind the GLFW build flag.
* changing felt script to fetch flutter
* changing the clone_flutter.sh code
* running integration tests with felt on cirrus. fetch framework in CI (not in local).
* only run cirrus tests on chrome. fix a comma in the flutter command path
* adding comments to public flags
* use local engine parameter for flutter pub get
* change flutter executable used for flutter drive command
* fix a cleanup issue. address comments. add toolException. enable web in flutter
* address reviwer comments. fix issue with local-engine
* address reviwer comments. fix issue with local-engine
* using engine/flutter/.dart_tools as clone directory. enabling clone script for local usage
* clean flutter repo with felt clean. add a flag to skip cloning the repo. always clone the repo even for local development, unless this flag is set
* fixing typos. updating readme for the new flag.
* fix directory error
* addressing reviewer comments
Fuchsia is the main consumer of these CIPD packages and - to simplify
its infrastructure - it is migrating its SDK partners over to producing
a CIPD package containing a flat .build-id directory.
This change also updates the CIPD package so that the .build-id
directory is placed at the root.
Bug: fxbug.dev/41443
Fuchsia is the main consumer of these CIPD packages and - to simplify
its infrastructure - it is migrating its SDK partners over to producing
a CIPD package containing a flat .build-id directory.
This change also updates the CIPD package so that the .build-id
directory is placed at the root.
Bug: fxbug.dev/41443
Fuchsia is the main consumer of these CIPD packages and - to simplify
its infrastructure - it is migrating its SDK partners over to producing
a CIPD package containing a flat .build-id directory.
This change also updates the CIPD package so that the .build-id
directory is placed at the root.
Bug: fxbug.dev/41443
The use of this macro in C++ translation units leads to the symbol visibility
being switched to default instead of hidden. This only happens in bitcode
enabled builds. A toolchain upgrade will be necessary to undo this workaround.
* script for fetching correct flutter version
* change cirrus yml for the script location
* change location of the script. Add it to tools
* cirrus still does not see the script. repeat path change from the previous step
* Looks like script worked correctly. do not change directory.
* change directory back to build root after scriot is run
* script runs ok. Still not able to find the bin directory. go all the way back
* still can't see the bin directory. carry the script content to cirrus.yml to debug better
* get the last commit id of the right repository
* content of the script worked in cirrus. call the script from tools
* cannot find the script under tools
* print the current path in the script to see why cirrus cannot see bin directory
* move to flutter path before running update packages
* tests run now. remove print outs
* error if the ENGINE_PATH is not set. exit the script
* addressing reviewer comments
* engine branch name on cirrus logs doesn't make sense
* fix typo
* change the directory of branch calculation
* remove extra logs
* addressing PR comments. Testing CIRRUS_CI env variable
* adding CIRRUS_CI check
This was only necessary when the Engine had to build in multiple buildroots
where the sources where checked out at different paths relative to the
buildroot. This is no longer the case and there are already cases GN rules
have been written that mix and match variable usage with the direct
specification of the path to the Flutter sources relative to the sole buildroot.
