- 14 Jan, 2021 1 commit
-
-
Yusuke Arakawa authored
-
- 03 Dec, 2020 1 commit
-
-
Ian Hickson authored
In principle this is backwards compatible; I just merged all the classes into one and deprecated everything that became redundant as a result.
-
- 02 Dec, 2020 1 commit
-
-
Emmanuel Garcia authored
-
- 01 Dec, 2020 1 commit
-
-
Chris Yang authored
[flutter_tools] Display "no platforms" message based on results when creating plugins project (#70215)
-
- 23 Nov, 2020 1 commit
-
-
Amir Hardon authored
This reverts commit 8e73bab9.
-
- 20 Nov, 2020 1 commit
-
-
Emmanuel Garcia authored
-
- 18 Nov, 2020 1 commit
-
-
stuartmorgan authored
Removes a comment that is left over from early iterations of the template.
-
- 14 Nov, 2020 1 commit
-
-
Jonah Williams authored
This reverts commit 8749d955.
-
- 13 Nov, 2020 1 commit
-
-
Ian Hickson authored
In principle this is backwards compatible; I just merged all the classes into one and deprecated everything that became redundant as a result.
-
- 22 Oct, 2020 1 commit
-
-
stuartmorgan authored
The template uses strcmp (to check the received method), so should include <cstring>
-
- 19 Oct, 2020 1 commit
-
-
Michael Thomsen authored
-
- 30 Sep, 2020 1 commit
-
-
stuartmorgan authored
-
- 25 Aug, 2020 2 commits
-
-
stuartmorgan authored
The pointer-argument-based version of Success() is deprecated; this updates the template to use the new reference-based version (which allows for inline construction of the response value). Part of https://github.com/flutter/flutter/issues/63975
-
Jenn Magder authored
-
- 14 Aug, 2020 1 commit
-
-
Juyeong Lee authored
-
- 11 Aug, 2020 1 commit
-
-
xster authored
-
- 04 Aug, 2020 3 commits
-
-
Chris Yang authored
-
Jonah Williams authored
This reverts commit 5b3dc525.
-
xster authored
-
- 30 Jul, 2020 1 commit
-
-
Ayush Bherwani authored
-
- 11 Jul, 2020 1 commit
-
-
xster authored
-
- 08 Jul, 2020 1 commit
-
-
Jonah Williams authored
Gives plugin and package a constraint on the flutter version, which will be from 2 stable's ago when this goes to stable. Adds an upper bound of 2.0
-
- 06 Jul, 2020 1 commit
-
-
stuartmorgan authored
* First pass at CMake files; untested * First pass of adding CMake generation logic on Windows * Misc fixes * Get bundling working, start incoprorating CMake build into tool * Fix debug, exe name. * Add resources * Move cmake.dart * Rip out all the vcxproj/solution plumbing * Fix plugin cmake generation * Build with cmake rather than calling VS directly * Adjust Windows plugin template to match standard header directory structure * Pass config selection when building * Partially fix multi-config handling * Rev template version * Share the CMake generation instead of splitting it out * VS build/run cycle works, with slightly awkward requirement to always build all * Update manifest * Plugin template fixes * Minor adjustments * Build install as part of build command, instead of separately * Test cleanup * Update Linux test for adjusted generated CMake approach * Plugin test typo fix * Add missing stub file for project test * Add a constant for VS generator
-
- 24 Jun, 2020 1 commit
-
-
Chris Yang authored
-
- 23 Jun, 2020 1 commit
-
-
David Iglesias authored
-
- 16 Jun, 2020 1 commit
-
-
stuartmorgan authored
Updates the tooling to use the GTK embedding, rather than the GLFW embedding: - Adds new requirements to `doctor` - Updates the app and plugin templates to make GTK-based runners and plugins - Stops downloading and installing the GLFW artifacts Final part of #54860, other than cleanup.
-
- 11 Jun, 2020 1 commit
-
-
Marcus Tomlinson authored
* Explicitly install the Flutter library * Publish ${FLUTTER_LIBRARY} to parent scope * Bundle plugin libraries * Bundle <plugin_name>_bundled_libraries too * BUNDLED_LIBRARIES -> PLUGIN_BUNDLED_LIBRARIES * Update Linux plugin test * Address review comments
-
- 27 May, 2020 1 commit
-
-
stuartmorgan authored
The CMake plugin build wasn't setting visibility to hidden by default, which meant that plugins exported everything by default. This would make bad interactions between plugins much more likely; only the intended API should be exported by the shared library.
-
- 16 May, 2020 1 commit
-
-
stuartmorgan authored
Updates the Linux templates to use CMake+ninja, rather than Make, and updates the tooling to generate CMake support files rather than Make support files, and to drive the build using cmake and ninja. Also updates doctor to check for cmake and ninja in place of make. Note: While we could use CMake+Make rather than CMake+ninja, in testing ninja handled the tool_backend.sh call much better, calling it only once rather than once per dependent target. While it does add another dependency that people are less likely to already have, it's widely available in package managers, as well as being available as a direct download. Longer term, we could potentially switch from ninja to Make if it's an issue. Fixes #52751
-
- 22 Apr, 2020 1 commit
-
-
xster authored
remove intellij references to the v1 embedding jars now that the v2 embeddings are referenced via maven (#55353)
-
- 07 Apr, 2020 1 commit
-
-
stuartmorgan authored
Updates Windows and Linux templates to use the new PluginRegistrarManager, improving lifetime handling and reducing boilerplate.
-
- 23 Mar, 2020 1 commit
-
-
stuartmorgan authored
Adds initial support for flutter create of apps and plugins. This is derived from the current FDE example app and sample plugin, adding template values where relevant. Since the APIs/tooling/template aren't stable yet, the app template includes a version marker, which will be updated each time there's a breaking change. The build now checks that the template version matches the version known by that version of the tool, and gives a specific error message when there's a mismatch, which improves over the current breaking change experience of hitting whatever build failure the breaking change causes and having to figure out that the problem is that the runner is out of date. It also adds a warning to the create output about the fact that it won't be stable. Plugins don't currently have a version marker since in practice this is not a significant problem for plugins yet the way it is for runners; we can add it later if that changes. Fixes #30704
-
- 19 Mar, 2020 1 commit
-
-
Michael Thomsen authored
-
- 11 Mar, 2020 1 commit
-
-
Emmanuel Garcia authored
-
- 03 Mar, 2020 1 commit
-
-
stuartmorgan authored
Adds initial support for `flutter create` of apps and plugins. This is derived from the current FDE example app and sample plugin, with a few changes: - Added template values where it makes sense. - Moved some likely-to-change values into separate files for now, to simplify the delete/recreate cycle that will be necessary until it's stable. - Added some minor Makefile flag handling improvements Since the APIs/tooling/template aren't stable yet, the app template includes a version marker, which will be updated each time there's a breaking change. The build now checks that the template version matches the version known by that version of the tool, and gives a specific error message when there's a mismatch, which improves over the current breaking change experience of hitting whatever build failure the breaking change causes and having to figure out that the problem is that the runner is out of date. It also adds a warning to the `create` output about the fact that it won't be stable.
-
- 28 Feb, 2020 1 commit
-
-
stuartmorgan authored
Now that the new schema is supported on the stable channel, and the old schema is considered legacy, the template should always create plugins using the new schema.
-
- 13 Feb, 2020 1 commit
-
-
Dan Field authored
* drop unnecessary test deps * bump to junit 4.13
-
- 10 Feb, 2020 1 commit
-
-
Dan Field authored
-
- 30 Jan, 2020 2 commits
-
-
Greg Spencer authored
This reverts commit 9d4a35ba because it appears to break the gradle_non_android_plugin_test.
-
stuartmorgan authored
Now that the new schema is supported on the stable channel, and the old schema is considered legacy, the template should always create plugins using the new schema.
-