commit | 3d9ce3f1306efea7c7514b3e0ad4ff203c65e76d | [log] [tgz] |
---|---|---|
author | godofredoc <godofredoc@google.com> | Tue Sep 12 09:08:04 2023 -0700 |
committer | GitHub <noreply@github.com> | Tue Sep 12 09:08:04 2023 -0700 |
tree | 3cc62e11c8ba6173a5c14e4a568f387fa0564876 | |
parent | 6e71c38443c0bf9d8954c87bf69bb4e019f44f94 [diff] |
CP: Libwebp build script updates needed for the roll to 1.3.1 (#764) (#770) CP: https://github.com/flutter/buildroot/commit/7154eae5b1e161b064996fcc70e8be85298b8574 CP: 9780f253156165c515962f5f0c56235d34617689 ## Pre-launch Checklist - [X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [X] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [X] I read the [Flutter Style Guide] _recently_, and have followed its advice. - [X] I signed the [CLA]. - [X] I listed at least one issue that this PR fixes in the description above. - [X] I updated/added relevant documentation (doc comments with `///`). - [X] I added new tests to check the change I am making, or this PR is [test-exempt]. - [X] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/wiki/Tree-hygiene#overview [Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene [test-exempt]: https://github.com/flutter/flutter/wiki/Tree-hygiene#tests [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/wiki/Chat --------- Co-authored-by: Jason Simmons <jason-simmons@users.noreply.github.com>
Build environment for the Flutter engine
This repository is used by the flutter/engine repository. For instructions on how to use it, see that repository's CONTRIBUTING.md file.
To update your checkout to use the latest buildroot, run gclient sync
.
To submit patches to this buildroot repository, create a branch, push to that branch, then submit a PR on GitHub for that branch.
To point the engine to a new version of buildroot after your patch is merged, update the buildroot hash in the engine's DEPS file.