1. 10 Sep, 2023 1 commit
    • Daco Harkes's avatar
      Native assets support for MacOS and iOS (#130494) · aa36db1d
      Daco Harkes authored
      Support for FFI calls with `@Native external` functions through Native assets on MacOS and iOS. This enables bundling native code without any build-system boilerplate code.
      
      For more info see:
      
      * https://github.com/flutter/flutter/issues/129757
      
      ### Implementation details for MacOS and iOS.
      
      Dylibs are bundled by (1) making them fat binaries if multiple architectures are targeted, (2) code signing these, and (3) copying them to the frameworks folder. These steps are done manual rather than via CocoaPods. CocoaPods would have done the same steps, but (a) needs the dylibs to be there before the `xcodebuild` invocation (we could trick it, by having a minimal dylib in the place and replace it during the build process, that works), and (b) can't deal with having no dylibs to be bundled (we'd have to bundle a dummy dylib or include some dummy C code in the build file).
      
      The dylibs are build as a new target inside flutter assemble, as that is the moment we know what build-mode and architecture to target.
      
      The mapping from asset id to dylib-path is passed in to every kernel compilation path. The interesting case is hot-restart where the initial kernel file is compiled by the "inner" flutter assemble, while after hot restart the "outer" flutter run compiled kernel file is pushed to the device. Both kernel files need to contain the mapping. The "inner" flutter assemble gets its mapping from the NativeAssets target which builds the native assets. The "outer" flutter run get its mapping from a dry-run invocation. Since this hot restart can be used for multiple target devices (`flutter run -d all`) it contains the mapping for all known targets.
      
      ### Example vs template
      
      The PR includes a new template that uses the new native assets in a package and has an app importing that. Separate discussion in: https://github.com/flutter/flutter/issues/131209.
      
      ### Tests
      
      This PR adds new tests to cover the various use cases.
      
      * dev/devicelab/bin/tasks/native_assets_ios.dart
        * Runs an example app with native assets in all build modes, doing hot reload and hot restart in debug mode.
      * dev/devicelab/bin/tasks/native_assets_ios_simulator.dart
        * Runs an example app with native assets, doing hot reload and hot restart.
      * packages/flutter_tools/test/integration.shard/native_assets_test.dart
        * Runs (incl hot reload/hot restart), builds, builds frameworks for iOS, MacOS and flutter-tester.
      * packages/flutter_tools/test/general.shard/build_system/targets/native_assets_test.dart
        * Unit tests the new Target in the backend.
      * packages/flutter_tools/test/general.shard/ios/native_assets_test.dart
      * packages/flutter_tools/test/general.shard/macos/native_assets_test.dart
        * Unit tests the native assets being packaged on a iOS/MacOS build.
      
      It also extends various existing tests:
      
      * dev/devicelab/bin/tasks/module_test_ios.dart
         * Exercises the add2app scenario.
      * packages/flutter_tools/test/general.shard/features_test.dart
         * Unit test the new feature flag.
      aa36db1d
  2. 31 Aug, 2023 1 commit
    • chunhtai's avatar
      Removes ios universal link vmservices and let xcodeproject to dump js… (#133709) · 0b3b8cd5
      chunhtai authored
      …on file
      
      The deeplink validation tool will become an static app so it can't no longer access vm services.
      
      The goal will be then to turn them into flutter analyze command similar to `flutter analyze --android --[options]` that static app can use on.
      
      This pr only removes vm services and turn the api to dump a output file instead of printing everything to stdout.
      0b3b8cd5
  3. 18 Aug, 2023 1 commit
    • chunhtai's avatar
      Updates app link gradle tasks and remove vm services (#131805) · 61242fa1
      chunhtai authored
      1. Remove vm service registration
      2. combine print<variant>ApplicationId and print<variant>AppLinkDomain into one task dump<variant>AppLinkSettings, which dump all the data in a json file
      
      The deeplink validation tool will be a static app in devtool instead of regular app. A Static app doesn't require a running app; therefore, we can't call these API through vmservices. I decided to convert these API into flutter analyzer command, which will be done in a separate PR https://github.com/flutter/flutter/pull/131009.
      
      The reason these print tasks are converted into file dumps is to reduce the amount of data encoding and decoding. Instead of passing data through stdout, the devtool can read the files generated by gradle tasks instead.
      61242fa1
  4. 13 Jul, 2023 1 commit
  5. 07 Jun, 2023 1 commit
  6. 05 May, 2023 1 commit
  7. 04 May, 2023 1 commit
  8. 18 Apr, 2023 1 commit
  9. 27 Mar, 2023 1 commit
  10. 21 Mar, 2023 1 commit
  11. 06 Mar, 2023 1 commit
  12. 28 Feb, 2023 1 commit
  13. 27 Feb, 2023 2 commits
  14. 17 Feb, 2023 1 commit
  15. 13 Feb, 2023 1 commit
  16. 09 Feb, 2023 1 commit
  17. 01 Feb, 2023 1 commit
  18. 10 Jan, 2023 1 commit
  19. 15 Dec, 2022 1 commit
  20. 20 Sep, 2022 1 commit
  21. 07 Sep, 2022 1 commit
  22. 02 Sep, 2022 1 commit
  23. 31 Aug, 2022 1 commit
  24. 09 Aug, 2022 1 commit
  25. 27 Jul, 2022 1 commit
  26. 20 Jul, 2022 1 commit
  27. 18 Jul, 2022 1 commit
  28. 15 Jul, 2022 1 commit
  29. 24 Jun, 2022 1 commit
  30. 15 Jun, 2022 1 commit
  31. 26 May, 2022 1 commit
  32. 07 May, 2022 1 commit
  33. 27 Apr, 2022 2 commits
  34. 11 Apr, 2022 1 commit
  35. 31 Mar, 2022 1 commit
  36. 30 Mar, 2022 1 commit
  37. 29 Mar, 2022 1 commit
  38. 21 Mar, 2022 1 commit