- 09 Jul, 2020 1 commit
-
-
Robert Ancell authored
-
- 24 Jun, 2020 1 commit
-
-
stuartmorgan authored
Remove the version checking and associated warnings. The Linux template and build process will now be subject to more typical Flutter breaking change policy, and should no longer require regularly deleting and recreating the platform directory.
-
- 23 Jun, 2020 2 commits
-
-
Robert Ancell authored
Remove Linux shell window_configuration.cc/.h It was a temporary solution while the shell was changing.
-
stuartmorgan authored
-
- 18 Jun, 2020 2 commits
-
-
Robert Ancell authored
The previous call set the minimum size, not just the initial size.
-
Robert Ancell 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.
-
- 13 Jun, 2020 1 commit
-
-
stuartmorgan authored
This install step fails if the list is empty, which is the case for projects without plugins (or Dart-only plugins, so flutter/plugins presubmits are currently broken).
-
- 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
-
- 29 May, 2020 1 commit
-
-
Marcus Tomlinson authored
-
- 28 May, 2020 1 commit
-
-
stuartmorgan authored
BundleUtilities apparently doesn't do build-system-style timestamp analysis when deciding what to copy, and instead just doesn't copy things that are already present. This cleans that bundle directory on each build, so that it includes the up-to-date library versions. Since this is just copying from build artifacts, this is very fast; the build steps themselves are not affected. Fixes https://github.com/flutter/flutter/issues/58049
-
- 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.
-
- 21 May, 2020 1 commit
-
-
Ken VanDine authored
-
- 20 May, 2020 1 commit
-
-
stuartmorgan authored
Re-adds a line that was accidentally removed in #57515
-
- 18 May, 2020 1 commit
-
-
stuartmorgan authored
The Linux CMakeLists.txt are intended to be compatible with 3.10, but accedintally used a list construct that wasn't added until 3.12. This adds a custom replacement function. This makes the build compatible with 3.10 as originally intended.
-
- 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
-
- 10 May, 2020 1 commit
-
-
stuartmorgan 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.
-