- 29 Jan, 2021 1 commit
-
-
Jonah Williams authored
-
- 27 Jan, 2021 1 commit
-
-
Jonah Williams authored
* opt out the flutter tool * oops EOF * fix import * Update tool_backend.dart * Update daemon_client.dart * fix more
-
- 13 Jan, 2021 1 commit
-
-
Claire Davis authored
-
- 26 Oct, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 21 Oct, 2020 2 commits
-
-
Zachary Anderson authored
This reverts commit ae06c19a.
-
Alexandre Ardhuin authored
-
- 19 Oct, 2020 1 commit
-
-
Jenn Magder authored
-
- 06 Oct, 2020 1 commit
-
-
stuartmorgan authored
When the developer doesn't have permission to create symlinks, we display specific instructions, but they were only correct for recent versions of Windows 10. This improves them by: - Giving the correct instructions for older versions. - For recent versions, adds a command that will deep-link into the settings application so that developers don't have to figure out where/how to enable developer mode. Fixes https://github.com/flutter/flutter/issues/66973
-
- 30 Sep, 2020 1 commit
-
-
Jenn Magder authored
-
- 15 Sep, 2020 1 commit
-
-
stuartmorgan authored
-
- 09 Sep, 2020 1 commit
-
-
stuartmorgan authored
The Windows plugin CMake generation had code to ensure that the paths written to it used POSIX separators, but the Linux version didn't; that meant that plugin updates run on Windows machines would corrupt the generated (but checked in) Linux CMake file. This change shares that code so that both will use POSIX paths regardless of what OS they are generated on. Fixes https://github.com/flutter/flutter/issues/64591
-
- 20 Aug, 2020 1 commit
-
-
xster authored
-
- 12 Aug, 2020 1 commit
-
-
Jonah Williams authored
-
- 11 Jul, 2020 1 commit
-
-
xster authored
-
- 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
-
- 25 Jun, 2020 1 commit
-
-
Jonah Williams authored
The global packages path could cause tests to fail when it would be overriden to unexpected (in test setup) values. Remove most usage and make it a configuration on buildInfo, along with most other build information. Cleanup the asset builder to require the .packages path and the resident runners to no longer require it, since they already have the information in build_info. It needs to stick around for the fuchsia deps we do not control. Filled #60232 for remaining work.
-
- 24 Jun, 2020 1 commit
-
-
Chris Yang 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
-
- 18 May, 2020 1 commit
-
-
stuartmorgan authored
Treats 'pluginClass: none' as equivalent to having no 'pluginClass' entry on the desktop platforms, to satisy stable channel plugin validation of Dart-only desktop plugin implementations. See issue for full details. Part of https://github.com/flutter/flutter/issues/57497
-
- 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
-
-
Jonah Williams authored
-
- 03 Apr, 2020 1 commit
-
-
Francisco Magdaleno authored
-
- 06 Mar, 2020 1 commit
-
-
Dan Field authored
-
- 05 Mar, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 27 Feb, 2020 1 commit
-
-
stuartmorgan authored
When generating the plugin registrant for Linux, also generate a makefile that can be included in the app-level Makefile to manage all of the plugin targets and flags, exporting them in a few known variables for use in the outer makefile. Part of #32720
-
- 25 Feb, 2020 1 commit
-
-
stuartmorgan authored
Adds utility code for managing list of plugin projects within a solution file, updating them as the plugins change. This is a prototype of an approach to solution-level portion of Windows plugin tooling; it may not be what the final plugin handling on Windows uses, but it makes things much better in the short term, and gives us a baseline to evaluate other possible solution management systems against. Part of #32719
-
- 13 Feb, 2020 2 commits
-
-
stuartmorgan authored
Generates a Property Sheet for Windows builds containing link and include path information for any included plugins. This allows automating part of the process of integrating plugins into the build that is currently manual. To support this change, refactored msbuild_utils into a PropertySheet class so that it can be used to make different property sheets.
-
stuartmorgan authored
This makes ephemeral symlinks to each plugin, for use by build systems. This is similar to the logic implemented in the Podfile on iOS and macOS, but managed internally to the Flutter tool. Exploration for addressing #32719 and #32720 Related to #41146
-
- 11 Feb, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 29 Jan, 2020 1 commit
-
-
Emmanuel Garcia authored
-
- 17 Jan, 2020 2 commits
-
-
Francisco Magdaleno authored
-
Jenn Magder authored
This reverts commit 5eb394e0.
-
- 16 Jan, 2020 1 commit
-
-
Francisco Magdaleno authored
-
- 14 Jan, 2020 1 commit
-
-
xster authored
-
- 07 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
-
- 25 Nov, 2019 1 commit
-
-
Michael Klimushyn authored
There has been some confusion about whether or not .flutter-plugins-dependencies should be tracked in version control or not. Added a comment to both it and .flutter-plugins explaining that it's generated and shouldn't be. .flutter-plugins-dependencies is parsed through JSON, and the JSON spec doesn't support comments. So unfortunately the note is living in an arbitrary "_info" key instead of an obvious top level comment.
-
- 22 Nov, 2019 1 commit
-
-
Emmanuel Garcia authored
Add `.flutter-plugins-dependencies` to the project, which contains the app's plugin dependency graph (#45379)
-
- 11 Nov, 2019 1 commit
-
-
xster authored
-