1. 07 Mar, 2024 1 commit
    • Matej Knopp's avatar
      Fix frameworks added to bundle multiple times instead of lipo (#144688) · de728320
      Matej Knopp authored
      *Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.*
      
      *List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.*
      
      *If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
      de728320
  2. 05 Mar, 2024 1 commit
  3. 14 Feb, 2024 1 commit
  4. 08 Feb, 2024 1 commit
    • Daco Harkes's avatar
      Reland "Move native assets to `isolated/` directory" (#143055) · 4e70bfae
      Daco Harkes authored
      Reland of https://github.com/flutter/flutter/pull/142709.
      
      The revert of the revert is in the first commit, the fix in the commit on top.
      
      The move of the fakes for packages/flutter_tools/test/general.shard/resident_runner_test.dart was erroneous before, as it was trying to use setters instead of a private field. This PR changes the private `_devFS` field in the fake to be a public `fakeDevFS` in line with other fakes.
      
      ## Original PR description
      
      Native assets in other build systems are not built with `package:native_assets_builder` invoking `build.dart` scripts. Instead all packages have their own blaze rules. Therefore we'd like to not depend on `package:native_assets_builder` from flutter tools in g3 at all.
      
      This PR aims to move the imports of `native_assets_builder` and `native_assets_cli` into the `isolated/` directory and into the files with a `main` function that are not used in with other build systems.
      
      In order to be able to remove all imports in files used by other build systems, two new interfaces are added `HotRunnerNativeAssetsBuilder` and `TestCompilerNativeAssetsBuilder`. New parameters are then piped all the way through from the entry points:
      
      * bin/fuchsia_tester.dart
      * lib/executable.dart
      
      The build_system/targets dir is already excluded in other build systems.
      
      So, after this PR only the two above files and build_system/targets import from `isolated/native_assets/` and only `isolated/native_assets/` import `package:native_assets_cli` and `package:native_assets_builder`.
      
      Context:
      
      * https://github.com/flutter/flutter/issues/142041
      4e70bfae
  5. 07 Feb, 2024 1 commit
    • auto-submit[bot]'s avatar
      Reverts "Move native assets to `isolated/` directory" (#143027) · ceca6066
      auto-submit[bot] authored
      Reverts flutter/flutter#142709
      
      Initiated by: vashworth
      
      Reason for reverting: `Mac tool_tests_general` started failing on this commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20tool_tests_general/15552/overview
      
      Original PR Author: dcharkes
      
      Reviewed By: {christopherfujino, chingjun, reidbaker}
      
      This change reverts the following previous change:
      Original Description:
      Native assets in other build systems are not built with `package:native_assets_builder` invoking `build.dart` scripts. Instead all packages have their own blaze rules. Therefore we'd like to not depend on `package:native_assets_builder` from flutter tools in g3 at all.
      
      This PR aims to move the imports of `native_assets_builder` and `native_assets_cli` into the `isolated/` directory and into the files with a `main` function that are not used in with other build systems.
      
      In order to be able to remove all imports in files used by other build systems, two new interfaces are added `HotRunnerNativeAssetsBuilder` and `TestCompilerNativeAssetsBuilder`. New parameters are then piped all the way through from the entry points:
      
      * bin/fuchsia_tester.dart
      * lib/executable.dart
      
      The build_system/targets dir is already excluded in other build systems.
      
      So, after this PR only the two above files and build_system/targets import from `isolated/native_assets/` and only `isolated/native_assets/` import `package:native_assets_cli` and `package:native_assets_builder`.
      
      Context:
      
      * https://github.com/flutter/flutter/issues/142041
      ceca6066
  6. 06 Feb, 2024 1 commit
    • Daco Harkes's avatar
      Move native assets to `isolated/` directory (#142709) · a069e62e
      Daco Harkes authored
      Native assets in other build systems are not built with `package:native_assets_builder` invoking `build.dart` scripts. Instead all packages have their own blaze rules. Therefore we'd like to not depend on `package:native_assets_builder` from flutter tools in g3 at all.
      
      This PR aims to move the imports of `native_assets_builder` and `native_assets_cli` into the `isolated/` directory and into the files with a `main` function that are not used in with other build systems.
      
      In order to be able to remove all imports in files used by other build systems, two new interfaces are added `HotRunnerNativeAssetsBuilder` and `TestCompilerNativeAssetsBuilder`. New parameters are then piped all the way through from the entry points:
      
      * bin/fuchsia_tester.dart
      * lib/executable.dart
      
      The build_system/targets dir is already excluded in other build systems.
      
      So, after this PR only the two above files and build_system/targets import from `isolated/native_assets/` and only `isolated/native_assets/` import `package:native_assets_cli` and `package:native_assets_builder`.
      
      Context:
      
      * https://github.com/flutter/flutter/issues/142041
      a069e62e