1. 11 Oct, 2023 1 commit
  2. 27 Sep, 2023 1 commit
  3. 26 Sep, 2023 1 commit
  4. 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
  5. 19 May, 2023 1 commit
  6. 20 Jan, 2023 1 commit
  7. 02 Dec, 2022 1 commit
    • Jackson Gardner's avatar
      Platform binaries reland (#115502) · db1c3e20
      Jackson Gardner authored
      You can now specify a --local-web-sdk flag to point to a wasm_release folder. This will make it so that only artifacts that pertain to the web sdk are overridden to point to the wasm_release folder. Other artifacts (such as impellerc) will pull from the cache, or from the --local-engine path if that is specified.
      
      This also uses precompiled platform kernel files for both ddc and dart2js
      db1c3e20
  8. 20 May, 2022 1 commit
  9. 18 May, 2022 1 commit
  10. 27 Apr, 2022 1 commit
  11. 29 Mar, 2022 1 commit
  12. 21 Mar, 2022 1 commit
  13. 02 Mar, 2022 1 commit
    • gaaclarke's avatar
      Starts using the `--source` flag to compile the dart registrant. (#98046) · fdcd1446
      gaaclarke authored
      * Starts using the `--source` flag to compile the dart registrant.
      
      * updated general.shard tests
      
      * Fixed the resident compiler flow
      
      * added integration test
      
      * made the integration test self contained
      
      * renamed generated_main to dart_plugin_registrant
      
      * cleaned up for review
      
      * added task runner for ci
      
      * added bringup and TESTOWNERS
      
      * updated failure message
      fdcd1446
  14. 24 May, 2021 1 commit
  15. 23 Apr, 2021 2 commits
  16. 08 Apr, 2021 1 commit
  17. 12 Mar, 2021 1 commit
  18. 10 Mar, 2021 1 commit
  19. 08 Feb, 2021 1 commit
  20. 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
  21. 27 Jan, 2021 1 commit
  22. 03 Dec, 2020 1 commit
  23. 16 Oct, 2020 1 commit
  24. 09 Oct, 2020 1 commit
  25. 23 Sep, 2020 2 commits
  26. 22 Sep, 2020 1 commit
  27. 24 Jun, 2020 1 commit
  28. 03 Jun, 2020 2 commits
  29. 27 May, 2020 1 commit
  30. 06 May, 2020 1 commit
  31. 20 Apr, 2020 1 commit
  32. 27 Jan, 2020 1 commit
  33. 06 Jan, 2020 1 commit
  34. 27 Nov, 2019 1 commit
    • Ian Hickson's avatar
      License update (#45373) · 449f4a66
      Ian Hickson authored
      * Update project.pbxproj files to say Flutter rather than Chromium
      
      Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright.
      
      * Update the copyright notice checker to require a standard notice on all files
      
      * Update copyrights on Dart files. (This was a mechanical commit.)
      
      * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine.
      
      Some were already marked "The Flutter Authors", not clear why. Their
      dates have been normalized. Some were missing the blank line after the
      license. Some were randomly different in trivial ways for no apparent
      reason (e.g. missing the trailing period).
      
      * Clean up the copyrights in non-Dart files. (Manual edits.)
      
      Also, make sure templates don't have copyrights.
      
      * Fix some more ORGANIZATIONNAMEs
      449f4a66
  35. 24 Nov, 2019 1 commit
  36. 15 Nov, 2019 1 commit
  37. 10 Nov, 2019 1 commit