- 20 Aug, 2019 2 commits
-
-
Zachary Anderson authored
-
stuartmorgan authored
Switch from the un-suffixed Windows and Linux libraries to the _glfw-suffixed versions, in preparation for having non-GLFW versions using the previous library/wrapper names. Part of #38589
-
- 19 Aug, 2019 1 commit
-
-
Michael Thomsen authored
-
- 17 Aug, 2019 1 commit
-
-
Todd Volkert authored
We were using the `defaults` command-line utility to parse Plist files, but it was never supported by Apple, and it appears that in an upcoming OS release, it will be less likely to work: > WARNING: The defaults command will be changed in an upcoming > major release to only operate on preferences domains. General > plist manipulation utilities will be folded into a different > command-line program. Fixes https://github.com/flutter/flutter/issues/37701
-
- 16 Aug, 2019 1 commit
-
-
Jonah Williams authored
-
- 15 Aug, 2019 5 commits
-
-
Jonah Williams authored
-
Zachary Anderson authored
-
Zachary Anderson authored
-
Ingo Reinhart authored
-
Dan Field authored
-
- 13 Aug, 2019 1 commit
-
-
Christopher Fujino authored
-
- 10 Aug, 2019 1 commit
-
-
jmagman authored
-
- 09 Aug, 2019 1 commit
-
-
Yegor authored
update dependencies; add a Web smoke test
-
- 08 Aug, 2019 1 commit
-
-
Jonah Williams authored
-
- 07 Aug, 2019 2 commits
-
-
Jason Simmons authored
The use-application-binary flag can be used to run a previously built app package.
-
Emmanuel Garcia authored
-
- 06 Aug, 2019 1 commit
-
-
sjindel-google authored
This PR contains the tests for flutter/engine#10186.
-
- 05 Aug, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
-
Jonah Williams authored
-
- 01 Aug, 2019 3 commits
-
-
Majid Hajian authored
-
Jonah Williams authored
-
Zachary Anderson authored
-
- 31 Jul, 2019 1 commit
-
-
Jonah Williams authored
-
- 30 Jul, 2019 1 commit
-
-
Dan Field authored
-
- 29 Jul, 2019 2 commits
-
-
Jonah Williams authored
-
Zachary Anderson authored
-
- 25 Jul, 2019 1 commit
-
-
Jonah Williams authored
-
- 24 Jul, 2019 7 commits
-
-
Jonah Williams authored
-
Matt Carroll authored
-
Jonah Williams authored
-
Jonah Williams authored
-
Jiahao authored
An optimization to the coverage collection speed was added in #30811. This commit further expands on it to parameterize the CoverageCollector with a custom predicate, allowing internal use cases to filter the RPC calls to the Dart VM based on scripts of interest to coverage collection.
-
Ian Hickson authored
-
Zachary Anderson authored
-
- 23 Jul, 2019 4 commits
-
-
Jonah Williams authored
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
Emmanuel Garcia authored
This reverts commit 11460b83.
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
- 22 Jul, 2019 1 commit
-
-
Jonah Williams authored
-