- 14 Dec, 2023 1 commit
-
-
Daco Harkes authored
Update Android SDK from 33 to 34. Following the engine update: * https://github.com/flutter/engine/pull/47839
-
- 13 Dec, 2023 1 commit
-
-
Reid Baker authored
- Use copy task that branches for 8.3 and above to avoid using project.exec in a dolast block. part 1/n for flutter/flutter/issues/138523 This PR does not test the 8.3 branch but instead builds the ability to write a branching gradle test. After fixing this project.exec action there I discovered a second that needs to be removed or migrated in order for the build to work. Related reading https://docs.gradle.org/8.0/userguide/configuration_cache.html#config_cache:requirements https://docs.gradle.org/current/javadoc/org/gradle/process/ExecOperations.html (not used but considered) https://docs.gradle.org/8.2/dsl/org.gradle.api.tasks.Copy.html#org.gradle.api.tasks.Copy:fileMode
-
- 07 Dec, 2023 1 commit
-
-
Daco Harkes authored
Support for FFI calls with `@Native external` functions through Native assets on Android. 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 Android. Mainly follows the design of the previous PRs. For Android, we detect the compilers inside the NDK inside SDK. And bundling of the assets is done by the flutter.groovy file. The `minSdkVersion` is propagated from the flutter.groovy file as well. The NDK is not part of `flutter doctor`, and users can omit it if no native assets have to be build. However, if any native assets must be built, flutter throws a tool exit if the NDK is not installed. Add 2 app is not part of this PR yet, instead `flutter build aar` will tool exit if there are any native assets.
-
- 20 Jan, 2023 1 commit
-
-
Michael Goderbauer authored
-
- 28 Jul, 2022 1 commit
-
-
Michael Goderbauer authored
-
- 27 Apr, 2022 1 commit
-
-
Alexandre Ardhuin authored
-
- 13 Jan, 2022 1 commit
-
-
Emmanuel Garcia authored
* Bump video_player in flutter gallery * Update packages * Update dependencies * Bump device_info * Update dev/devicelab/bin/tasks/build_ios_framework_module_test.dart Co-authored-by: Jenn Magder <magder@google.com> * Update dev/devicelab/bin/tasks/module_custom_host_app_name_test.dart Co-authored-by: Jenn Magder <magder@google.com> * Update dev/devicelab/bin/tasks/module_test.dart Co-authored-by: Jenn Magder <magder@google.com> * Remove deprecated device_info from ios-frameworks test Co-authored-by: Jenn Magder <magder@google.com>
-
- 13 Jul, 2021 1 commit
-
-
Darren Austin authored
-
- 05 Jun, 2021 1 commit
-
-
Jenn Magder authored
-
- 27 Apr, 2021 1 commit
-
-
xster authored
-
- 16 Dec, 2020 1 commit
-
-
xster authored
-
- 15 Dec, 2020 1 commit
-
-
xster authored
-
- 07 Oct, 2020 1 commit
-
-
Casey Hillers authored
-
- 22 Sep, 2020 1 commit
-
-
godofredoc authored
-
- 16 Sep, 2020 1 commit
-
-
Michael R Fairhurst authored
-
- 19 Aug, 2020 1 commit
-
-
xster authored
-
- 11 Jul, 2020 1 commit
-
-
xster authored
-
- 17 Feb, 2020 1 commit
-
-
shihchanghsiungsonos authored
-
- 11 Feb, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 22 Jan, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 27 Nov, 2019 1 commit
-
-
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
-
- 19 Nov, 2019 1 commit
-
-
Jonah Williams authored
-
- 09 Nov, 2019 1 commit
-
-
Ian Hickson authored
-
- 08 Nov, 2019 1 commit
-
-
Jonah Williams authored
Removes multiple re-entrant calls of bundle and aot and replaces them with a single call to assemble. This restores full caching and will allow follow-up performance improvements when building multiple ABIs
-
- 07 Nov, 2019 1 commit
-
-
xster authored
-
- 25 Oct, 2019 1 commit
-
-
Michael Klimushyn authored
This will prevent the test from flaking based on updates to either package.
-
- 21 Oct, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 17 Oct, 2019 1 commit
-
-
Emmanuel Garcia authored
* Test the Android embedding v2 * Update integration tests * Split into shards
-
- 25 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 07 Aug, 2019 1 commit
-
-
Emmanuel Garcia 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 } }
-
- 17 Jul, 2019 1 commit
-
-
xster authored
-
- 10 Mar, 2019 1 commit
-
-
Dan Field authored
* Run non-perf sensisitive tests on Cirrus
-
- 10 Oct, 2018 1 commit
-
-
Greg Spencer authored
We decided that redefining the default for templates was premature. We're going to go back to having "module" in experimental land again, and we'll try again when we have the feature set fully baked. This keeps the writing of the .metadata files, and writing the template type to them, because that was a good improvement, and there are still a bunch of added tests that improve our coverage.
-
- 04 Oct, 2018 2 commits
-
-
Greg Spencer authored
I missed some create template conversions in the devicelab directory.
-
Alexandre Ardhuin authored
-
- 25 Sep, 2018 1 commit
-
-
Mikkel Nygaard Ravn authored
* Prototype * Fix paths to Flutter library resources * Invoke pod install as necessary for materialized modules * Add devicelab test for module use on iOS * Remove debug output * Rebase, reame materialize editable * Add devicelab test editable iOS host app * Removed add2app test section
-
- 19 Sep, 2018 1 commit
-
-
Danny Tuppeny authored
This fixes the devicelab failure after #22006 renamed this command.
-