1. 30 Nov, 2017 1 commit
  2. 30 Oct, 2017 1 commit
    • Adam Barth's avatar
      Don't collect usage data during Fuchsia build (#12780) · 21145144
      Adam Barth authored
      Previously, the usage analytics would generate a write to the user's
      HOME directory during the Fuchsia build. We're tightening down the
      environment in which we run the Fuchsia build, and these writes are now
      more obvious.
      
      This patch removes the usage analytics during the Fuchsia build,
      avoiding the write to the user's HOME directory.
      21145144
  3. 28 Oct, 2017 1 commit
  4. 22 Oct, 2017 1 commit
  5. 16 Oct, 2017 1 commit
  6. 26 Sep, 2017 1 commit
  7. 21 Sep, 2017 1 commit
  8. 21 Jun, 2017 1 commit
  9. 13 Jun, 2017 1 commit
  10. 05 May, 2017 1 commit
  11. 27 Apr, 2017 1 commit
  12. 20 Apr, 2017 1 commit
  13. 06 Apr, 2017 1 commit
  14. 23 Mar, 2017 2 commits
    • P.Y. Laligand's avatar
    • Chris Bracken's avatar
      Build Flutter app as a framework on iOS (#8971) · 0ee3f57a
      Chris Bracken authored
      **THIS IS A BREAKING CHANGE.** See below for migration steps for
      existing projects.
      
      Previously, Flutter app code was built as a raw dylib on iOS.  Dynamic
      libraries outside of a framework bundle are not supported on iOS, except
      for the system Swift libraries provided by Xcode.
      
      See:
      https://developer.apple.com/library/content/technotes/tn2435/_index.html#//apple_ref/doc/uid/DTS40017543-CH1-TROUBLESHOOTING_BUNDLE_ERRORS-EMBEDDED__DYLIB_FILES
      
      * Migrates Xcode build from app.dylib to App.framework
      * Migrates flutter create template
      * Migrates example projects
      
      Migration steps for existing projects
      =====================================
      
      The following steps should be taken from the root of your Flutter
      project:
      
      1. Edit `ios/.gitignore`: add `/Flutter/App.framework` on a new line.
      2. In the Xcode project navigator, remove `app.dylib` from the Flutter
         folder. Delete this file from the `ios/Flutter` directory in your project.
      3. Run a build to generate `ios/Flutter/App.framework`. From the command
         line, run `flutter build ios`. If you have not configured app signing
         in Xcode, an alternative method is to open the simulator, then run
         `flutter run -d iP`.
      4. In the Xcode project navigator, select the `Runner` project. In the
         project settings that are displayed in the main view, ensure that the
         `Runner` target is selected. You can verify this by exposing the
         sidebar using the [| ] icon in the upper-left corner of the main
         view.
      5. Select the *General* tab in the project settings. Under the
         *Embedded Binaries* section, click '+' to add `App.framework`. In the
         sheet that drops down, click the *Add Other...* button. Navigate to
         the `ios/Flutter` directory and select `App.framework`. Click *Open*.
         In the sheet that drops down, select *Create folder references*, then
         click *Finish*.
      6. In the project settings, verify that `App.framework` has been added to the
         *Embedded Binaries* and *Linked Frameworks and Libraries* lists.
      7. In the Xcode project navigator, drag `App.framework` under the
         Flutter folder.
      8. In the Xcode project navigator, select `Flutter` then from the
         *File* menu, select *Add Files to "Runner"...*. Navigate to the
         `ios/Flutter` directory, select `AppFrameworkInfo.plist` and click
         the *Add* button.
      9. From the command line, in your project directory, run
         `flutter build clean`, then `flutter run`.
      
      At this point your project should be fully migrated.
      0ee3f57a
  15. 14 Mar, 2017 1 commit
  16. 13 Mar, 2017 1 commit
  17. 10 Mar, 2017 1 commit
  18. 04 Mar, 2017 1 commit
  19. 20 Feb, 2017 1 commit
  20. 17 Feb, 2017 1 commit
    • Chris Bracken's avatar
      Do not attempt to merge non-fat frameworks in Xcode build (#8251) · 36e3260b
      Chris Bracken authored
      * Do not attempt to merge non-fat frameworks in Xcode build
      
      During the Xcode build, we strip code irrelevant to the target
      architecture in frameworks used by the application. In the case of
      non-fat executables, no stripping occurs, so the frameworks can be used
      as-is. No merge & replace step is necessary.
      
      * fixup! Do not attempt to merge non-fat frameworks in Xcode build
      36e3260b
  21. 09 Feb, 2017 2 commits
  22. 07 Feb, 2017 2 commits
    • Chris Bracken's avatar
      Handle non-fat frameworks in iOS app framework thinning (#7950) · b16a515d
      Chris Bracken authored
      Support for thinning app frameworks to the target architecture was added
      in 708909fc. This commit adds support
      and error-checking for non-fat frameworks that are not of the target
      architecture. In such cases, we now fail the build, and emit an error
      message and the contents of lipo -info for the affected framework.
      b16a515d
    • Chris Bracken's avatar
      Thin iOS app frameworks to the target architecture (#7913) · 1926d111
      Chris Bracken authored
      * Support thinning iOS frameworks to supported architectures
      
      When building against frameworks that are distributed as
      multi-architecture fat binaries, we want to strip the frameworks we
      distribute down to only the architectures specified in $ARCHS.
      
      This patch adds:
      * The ability to specify commands to xcode_backend.sh (if none is
        specified, run BuildApp for backward compatibility).
      * A 'thin' command that invokes lipo to thin down the distributed as
        described above.
      
      * Add framework thinning step to iOS build
      
      Invokes xcode_backend.sh thin on the build application.
      
      * Limit architectures to arm64 in Xcode template
      
      Flutter does not yet support armv7 iOS devices. Limit the $ARCHS build
      variable to arm64 until then.
      1926d111
  23. 26 Jan, 2017 1 commit
  24. 23 Jan, 2017 1 commit
  25. 09 Jan, 2017 1 commit
  26. 07 Jan, 2017 1 commit
    • Todd Volkert's avatar
      Update flutter_tools to use package:file throughout (#7385) · 8bb27034
      Todd Volkert authored
      This removes direct file access from within flutter_tools
      in favor of using `package:file` via a `FileSystem` that's
      accessed via the `ApplicationContext`.
      
      This lays the groundwork for us to be able to easily swap
      out the underlying file system when running Flutter tools,
      which will be used to provide a record/replay file system,
      analogous to what we have for process invocations.
      8bb27034
  27. 30 Nov, 2016 1 commit
  28. 29 Nov, 2016 2 commits
  29. 23 Nov, 2016 1 commit
  30. 14 Nov, 2016 1 commit
    • Dan Rubel's avatar
      Refactor flutter command exit code - part 2 (#6817) · e384c0d9
      Dan Rubel authored
      * convert pubGet to throw ToolExit on non-zero exit code
      * convert commandValidator to throw ToolExit for non-zero exit code
      * convert flutter commands to throw ToolExit for non-zero exit code
      * use convenience method throwToolExit
      * only show "if this problem persists" for unusual exceptions
      e384c0d9
  31. 04 Nov, 2016 1 commit
  32. 03 Nov, 2016 1 commit
  33. 02 Nov, 2016 1 commit
    • Petr Hosek's avatar
      Use prebuilt Dart snapshot when assembling bundle (#6660) · 93a2d07c
      Petr Hosek authored
      This is causing issues when integratting Flutter into GN as the
      generated depfile refers to snapshot as the target instead of the
      bundle. We instead use a separate GN action to generate the
      snapshot use the Flutter compiler to only assemble the bundle.
      93a2d07c
  34. 20 Oct, 2016 1 commit
  35. 04 Oct, 2016 1 commit
  36. 01 Oct, 2016 1 commit