| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
iOS,macOS: Compile Swift with opt flags in opt builds (#191622) We never passed optimisation flags to `swiftc`, and the compiler's default is `-Onone`, so all of the Darwin embedders' Swift shipped unoptimised in profile and release, and `assert()`s triggered in shipping binaries, as seen in flutter/flutter#190909. This updates our optimisation gn configs to set equivalent `swiftflags` alongside the `cflags` we already set. For iOS that means `-Osize` (to match `-Os` for Obj-C/C++). For macOS, that means `-O` (to match `-O2` for Obj-C/C++, Swift just has -O, no -O2, -O3). For both, we set and `-Onone` for `:no_optimize`. When `is_debug` is true, we default to unopt. Swift `assert()` behaves like `FML_DCHECK` (active in unopt, compiled out in opt builds) and we should use `precondition()` where we'd use `FML_CHECK` -- i.e. cases we want to assert even in release builds. The following dev-specific asserts are now compiled out from shipped engines: * `DisplayLinkManager.shared` main-thread check * `KeyboardInsetManager` vsync client internal-state check * `FlutterRunLoop.mainRunLoop` the guard check already triggers * `TraceScope.deinit` ensure `end()` was called This also moves the main-thread check in `FlutterRunLoop.ensureMainLoopInitialized` to a `precondition`. Binding the main run loop to the wrong thread silently leaves everything later scheduled on it running on the wrong thread so we should continue to blow up in all modes. This change chops 130272 bytes (0.79%) off `Flutter.framework` on `ios_release`. Issue: https://github.com/flutter/flutter/issues/191616 Related: https://github.com/flutter/flutter/issues/190909 (demonstrates existing behaviour) No new tests, since this is a compile config change: the build *is* the test, along with not breaking the existing tests. <!-- Thanks for filing a pull request! Reviewers are typically assigned within a week of filing a request. To learn more about code review, see our documentation on Tree Hygiene: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md --> ## Pre-launch Checklist - [X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [X] I read the [AI contribution guidelines] and understand my responsibilities, or I am not using AI tools. - [X] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [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] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [X] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [AI contribution guidelines]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md | 12 天前 | |
Move the Fuchsia SDK to //third_party/fuchsia-sdk (#177118) The //third_party/fuchsia-sdk path is expected by the build scripts for other packages in the Chromium tree such as Abseil. | 10 个月前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Update Chromium sysroot to pick up RISC-V support. (#173671) Bug: https://github.com/flutter/flutter/issues/99963 | 11 个月前 | |
Rename apple -> darwin across our buildroot (#168558) As part of unifying our iOS and macOS build config, toolchain, and scripts, I named some of these `apple_sdk.py`, `toolchain/apple`, etc. for consistency with the chromium toolchain. This renames these `darwin` for consistency with other parts of our build. Issue: https://github.com/flutter/flutter/issues/167592 ## 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 and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [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] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [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/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
iOS: clean up swiftc.py after migration to target triples (#189240) In https://github.com/flutter/flutter/pull/189174, we migrated back to using target triples in swiftc.py in order to more closely mirror the commandline interface to `swiftc` itself. This is a followup that cleans up some extra function parameters that are no longer necessary now that we're getting the target triple in args. This cleans up a few remaining diffs from the reversion of the target triple splitting from https://github.com/flutter/flutter/pull/185712/changes#diff-d57f937ed2d743b17635dd069689072eba124f649f307228915c25d55b19ed62. No test changes since this is a refactor with no semantic change. The test is the build (and transitively, all the tests it builds and runs). Issue: https://github.com/flutter/flutter/issues/185741 ## Pre-launch Checklist - [X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [X] I read the [AI contribution guidelines] and understand my responsibilities, or I am not using AI tools. - [X] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [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] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [X] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [AI contribution guidelines]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md | 1 个月前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Roll Abseil to Chromium's 5b92b04a2e (based on Abseil commit fc4481e968) (#177059) This also moves the Abseil sources from //flutter/third_party to //third_party to allow use of Chromium's GN scripts without modification. See internal issue b/400498305 | 10 个月前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Roll Abseil to Chromium's 5b92b04a2e (based on Abseil commit fc4481e968) (#177059) This also moves the Abseil sources from //flutter/third_party to //third_party to allow use of Chromium's GN scripts without modification. See internal issue b/400498305 | 10 个月前 | |
Roll Abseil to Chromium's 5b92b04a2e (based on Abseil commit fc4481e968) (#177059) This also moves the Abseil sources from //flutter/third_party to //third_party to allow use of Chromium's GN scripts without modification. See internal issue b/400498305 | 10 个月前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Remove use of deprecated API related to removal of the VM isolate. (#187013) - Don't pass VM snapshot to Dart_Initialize. - Don't expect kDart{Vm,Isolate}Snapshot{Data,Instructions} symbols defined. - Replace 4-symbol Dart_LoadELF with 2-symbol Dart_LoadELF2. Blocking: https://dart-review.googlesource.com/c/sdk/+/502780 | 3 个月前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Roll ANGLE to a branch based on d9fa255a5c22 (#176747) See https://github.com/flutter/flutter/issues/174665 | 10 个月前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
Merge flutter/engine into framework Adds files from flutter/flaux which contain modifications for the engine structure. The history for engine/ has been edited. Please see flutter/engine for the original PRs. | 1 年前 | |
fix: missing MSVC 2022 (#180661) codefu wins the shamecube award for bad python. Tested on windows 11 enterprise + vc 2022: ```shell Searching for installed Visual Studio versions: 2019, 2017, 2022, 2026, 16.0, 15.0, 17.0, 18 vs_path = "C:\\Program Files/Microsoft Visual Studio/2022/Community" sdk_path = "C:\\Program Files (x86)\\Windows Kits\\10" vs_version = "2022" wdk_dir = "" runtime_dirs = "C:\\Windows\\System32;C:\\Windows\\SysWOW64;Arm64Unused" ``` fixes #180660 | 7 个月前 | |
Roll Abseil to Chromium's 5b92b04a2e (based on Abseil commit fc4481e968) (#177059) This also moves the Abseil sources from //flutter/third_party to //third_party to allow use of Chromium's GN scripts without modification. See internal issue b/400498305 | 10 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 12 天前 | ||
| 10 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 10 个月前 | ||
| 1 年前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 1 年前 | ||
| 3 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 10 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 10 个月前 |