- 23 Mar, 2017 1 commit
-
-
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.
-
- 14 Mar, 2017 1 commit
-
-
Chris Bracken authored
Making the directories read-only causes problems with deletion, which breaks the Mac chrome buildbot and DeviceLab. Followup patch to cb2b89c3.
-
- 13 Mar, 2017 1 commit
-
-
Chris Bracken authored
Provides a strong hint to developers that editing Flutter framework headers isn't supported.
-
- 10 Mar, 2017 1 commit
-
-
Chris Bracken authored
Use line-based iteration in place of word-based iteration over the framework directories, to avoid breaking on spaces.
-
- 17 Feb, 2017 1 commit
-
-
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
-
- 09 Feb, 2017 2 commits
-
-
Chris Bracken authored
Required to handle Flutter SDK (and other) paths that include spaces. Also includes general cleanup: * Declare explicitly that we use /bin/bash, since we rely on its features. * Add -- where possible, to avoid interpreting files starting in - as options. * Suppress output of pushd/popd. * Avoid stringifying arrays.
-
Chris Bracken authored
-
- 07 Feb, 2017 2 commits
-
-
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.
-
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.
-
- 25 Aug, 2016 1 commit
-
-
Chris Bracken authored
This change adds a top-level getBuildDirectory func and funcs for android, aot, asset, ios build products. Developers may now add a "build-dir" mapping to their ~/.flutter_settings (JSON format) config file. Output directory is relative to the main flutter application directory. This change also changes the default build directory for iOS builds to a subdirectory of the configured build directory, 'build/ios' by default.
-
- 23 Aug, 2016 1 commit
-
-
Chris Bracken authored
Previously, `flutter build` products were emitted to build/ and only xcode build products were emitted to $SYMROOT.
-
- 10 Jun, 2016 1 commit
-
-
Todd Volkert authored
-
- 06 Jun, 2016 1 commit
-
-
Adam Barth authored
The `flutter.buildMode` property now controls whether to build in debug, profiling, or release.
-
- 04 Jun, 2016 1 commit
-
-
Adam Barth authored
This patch sets a default path for Flutter.framework that's sensible based on the FLUTTER_MODE.
-
- 03 Jun, 2016 2 commits
-
-
Chinmay Garde authored
Add a FLUTTER_MODE variable to the generated Xcconfig and fix snapshot generation on all targets. (#4362) Get rid of the DART_EXPERIMENTAL_INTERPRETER_FLAG.
-
Adam Barth authored
This patch adds some sensible defaults to xcode_backend.sh and documents how to build hello_services for iOS using Xcode.
-
- 02 Jun, 2016 1 commit
-
-
Adam Barth authored
Fixes #4298
-
- 27 May, 2016 1 commit
-
-
Adam Barth authored
Instead of embedding Flutter.framework and BuildFlutterApp in the Xcode project, we store these in flutter.git, where we can reference them.
-