| commit | bce07474ce354afc8ea6bb1b695cc86ef376260d | [log] [tgz] |
|---|---|---|
| author | zijiehe@ <68449066+zijiehe-google-com@users.noreply.github.com> | Mon Mar 18 12:19:16 2024 -0700 |
| committer | GitHub <noreply@github.com> | Mon Mar 18 12:19:16 2024 -0700 |
| tree | 791e0d40414a445593142d8a27a1bd38d875689d | |
| parent | e9c4eebe21f45526ef3ec9ba6db5964268150279 [diff] |
[Fuchsia] remove build/fuchsia (#839) After https://github.com/flutter/engine/pull/51072, this folder is obsolete and can be removed. The change is locally tested. Bug: http://b/40935282 ## 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.