- 01 Nov, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 31 Oct, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 30 Oct, 2019 1 commit
-
-
Efthymis Sarmpanis authored
-
- 23 Oct, 2019 1 commit
-
-
Jonah Williams authored
-
- 22 Oct, 2019 2 commits
-
-
Jonah Williams authored
This reverts commit 3597bae6.
-
Ian Hickson authored
-
- 21 Oct, 2019 2 commits
-
-
Emmanuel Garcia authored
-
Jonah Williams authored
-
- 18 Oct, 2019 1 commit
-
-
Jonah Williams authored
-
- 15 Oct, 2019 1 commit
-
-
liyuqian authored
So we can test SkSL precompile using the command line tools. See https://github.com/flutter/engine/pull/12412.
-
- 11 Oct, 2019 1 commit
-
-
Ian Hickson authored
...because otherwise, processes that think they're manipulating your filesystem will be doing crazy things the test is ignoring, leading to (at best) failures and (at worst) flakes or disk corruption.
-
- 10 Oct, 2019 1 commit
-
-
Jonah Williams authored
-
- 07 Oct, 2019 1 commit
-
-
Ian Hickson authored
Applying our style guide: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#have-good-hygiene-when-using-temporary-directories
-
- 30 Sep, 2019 1 commit
-
-
Alexandre Ardhuin authored
* add missing trailing commas * add more missing trailing commas * add more and more missing trailing commas
-
- 27 Sep, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 24 Sep, 2019 3 commits
-
-
Emmanuel Garcia authored
-
Alexandre Ardhuin authored
-
Alexandre Ardhuin authored
-
- 23 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
This reverts commit 96482eeb.
-
- 20 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 14 Sep, 2019 2 commits
-
-
Emmanuel Garcia authored
-
Emmanuel Garcia authored
-
- 11 Sep, 2019 1 commit
-
-
Christopher Fujino authored
-
- 28 Aug, 2019 3 commits
-
-
Emmanuel Garcia authored
-
xster authored
-
Emmanuel Garcia 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
-
- 02 Aug, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 30 Jul, 2019 2 commits
-
-
Zachary Anderson authored
-
Zachary Anderson authored
-
- 23 Jul, 2019 3 commits
-
-
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 } }
-
- 18 Jul, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 13 Jul, 2019 1 commit
-
-
Ian Hickson authored
Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108)
-