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. 11 May, 2023 1 commit
  3. 28 Feb, 2023 1 commit
  4. 27 Feb, 2023 2 commits
  5. 17 Feb, 2023 1 commit
  6. 13 Feb, 2023 1 commit
  7. 15 Dec, 2022 1 commit
  8. 22 Nov, 2022 1 commit
  9. 09 Nov, 2022 1 commit
    • Victoria Ashworth's avatar
      Add more supported simulator debugging options and improve tests (#114628) · 3a656b16
      Victoria Ashworth authored
      * add debugging options to simulator, test more debugging flags, add tests for other launch arguements
      
      * refactor iOS launch arguments to use one function for both simulator and physical devices
      
      * treat dart flags differently between physical and simulator
      
      * Simplify some flags between devices.
      
      Change --disable-service-auth-codes to not always be included for physical devices, only if disableServiceAuthCodes is true.
      Change --disable-observatory-publication to be used for simulator devices too.
      Change --enable-checked-mode & --verify-entry-points to be used if debuggingEnabled is true regardless of device type.
      Chnage --trace-startup to be used for simulator devices too.
      
      * fix ios release mode with buildable app startApp test
      
      * determine observatory-port from deviceVmServicePort and hostVmServicePort
      
      * add comments and remove hasObservatoryPort
      3a656b16
  10. 27 Apr, 2022 1 commit
  11. 31 Mar, 2022 1 commit
  12. 13 Dec, 2021 1 commit
  13. 01 Nov, 2021 1 commit
  14. 17 Aug, 2021 1 commit
  15. 25 Jun, 2021 1 commit
  16. 03 Jun, 2021 1 commit
  17. 27 Apr, 2021 1 commit
  18. 21 Apr, 2021 1 commit
  19. 01 Apr, 2021 1 commit
  20. 31 Mar, 2021 1 commit
  21. 24 Mar, 2021 1 commit
  22. 16 Feb, 2021 1 commit
    • Jonah Williams's avatar
      [flutter_tools] use temp dir for tester dill, use desktop log reader (#75922) · 46b8ea8f
      Jonah Williams authored
      On windows, its not possible to run 2 integration tests using flutter-tester simultaneously. This is due to the flutter tester using a fixed location for its dill output. Use a temp dir instead.
      
      Also replace the custom log reader in flutter-tester with the desktop log reader, and ensure stopApp waits for the process exit code.
      
      Fixes #75534
      46b8ea8f
  23. 12 Feb, 2021 1 commit
  24. 08 Feb, 2021 1 commit
  25. 04 Feb, 2021 1 commit
    • Jonah Williams's avatar
      [flutter_tools] move process manager into tool (#75350) · 8b6baae4
      Jonah Williams authored
      Our current top crasher is an unclear error when ProcessManager fails to resolve an executable path. To fix this, we'd like to being adjusting the process resolution logic and adding more instrumentation to track failures. In order to begin the process, the ProcessManager has been folded back into the flutter tool
      8b6baae4
  26. 27 Jan, 2021 1 commit
  27. 17 Nov, 2020 1 commit
  28. 09 Nov, 2020 1 commit
  29. 23 Oct, 2020 1 commit
  30. 12 Oct, 2020 1 commit
    • Jonah Williams's avatar
      [flutter_tools] use fixed entry for dill uploads (#67837) · 0afddf35
      Jonah Williams authored
      For historical reasons, the flutter tool uploads dill files to paths based on the entrypoint URI. This isn't actually necessary, and the tool can use specific files : main.dart.incremental.dill for incremental dills, and main.dart.dill/main.dart.swap.dill for full dills. This allows hot restarting applications with an entrypoint outside of lib/ and simplifies the devFS code.
      
      Fixes #63243
      0afddf35
  31. 31 Aug, 2020 2 commits
  32. 29 Aug, 2020 1 commit
  33. 28 Aug, 2020 2 commits
  34. 27 Aug, 2020 1 commit
    • Ben Konyi's avatar
      Re-enable the Dart Development Service (DDS) (#64671) · d7d12412
      Ben Konyi authored
      This change re-enables DDS and outputs the DDS URI in place of the VM
      service URI on the console. If --disable-dds is not provided,
      --host-vmservice-port will be used to determine the port for DDS rather
      than the host port for the VM service, which will instead be randomly
      chosen.
      d7d12412
  35. 28 Jul, 2020 1 commit
  36. 10 Jul, 2020 1 commit
  37. 07 Jul, 2020 1 commit