mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
5a3f245710
Ensure that all Objective-C code in the codebase is being built with the standard set of Flutter Objective-C compiler flags with ARC enabled. Also bumps the cflags config up to the top of the first block within each target in which Objective-C sources appear, so that the location is consistent. Migrates The following targets to ARC, which had been missed in previous passes since they didn't declare the standard Flutter Obj-C[++] cflags: * `//flutter/fml:fml_unittests` * `//flutter/impeller/golden_tests:metal_screenshot` * `//flutter/impeller/playground:playground` * `//flutter/impeller/backend/metal:metal` * `//flutter/impeller/backend/metal:metal_unittests` * `//shell/gpu:gpu_surface_metal_unittests` * `//flutter/shell/platform/embedder:embedder_unittests` This patch includes no semantic changes. Issue: https://github.com/flutter/flutter/issues/137801 [C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
Engine Testing
This directory contains the infrastructure for running tests on the engine, which are most often run by Flutter's continuous integration (CI) systems.
The tests themselves are located in other directories, closer to the source for
each platform, language, and variant. For instance, macOS engine unit tests
written in objective C are located in the same directory as the source files,
but with a Test suffix added (e.g. "FlutterEngineTest.mm" holds the tests for
"FlutterEngine.mm", and they are located in the same directory).
Testing the Engine locally
If you are working on the engine, you will want to be able to run tests locally.
In order to learn the details of how do that, please consult the Flutter Wiki page on the subject.