- 04 Feb, 2022 1 commit
-
-
stuartmorgan authored
-
- 26 Jan, 2022 1 commit
-
-
Daco Harkes authored
-
- 14 Jan, 2022 1 commit
-
-
stuartmorgan authored
-
- 04 Jan, 2022 2 commits
-
-
Zachary Anderson authored
This reverts commit 5257f029.
-
Daco Harkes authored
* Building shared C source code as part of the native build for platforms Android, iOS, Linux desktop, MacOS desktop, and Windows desktop. * Sample code doing a synchronous FFI call. * Sample code doing a long running synchronous FFI call on a helper isolate. * Use of `package:ffigen` to generate the bindings.
-
- 04 Sep, 2021 1 commit
-
-
Chris Bracken authored
When we landed the CMake minimum requirement constraint for Visual Studio 2019, we landed it with minimum version 3.15, since that's what was shipping with the current version of VS 2019 at the time. Looking at the release notes of earlier versions, it's clear that earlier versions of Visual Studio 2019 shipped with version 3.14. See: https://devblogs.microsoft.com/cppblog/visual-studio-cmake-support-clang-llvm-cmake-3-14-vcpkg-and-performance-improvements/ Looking at release notes for CMake 3.15, there are no features/fixes introduced in that version that we are dependent on. https://cmake.org/cmake/help/latest/release/3.15.html Issue: https://github.com/flutter/flutter/issues/88589
-
- 18 Nov, 2020 1 commit
-
-
stuartmorgan authored
Removes a comment that is left over from early iterations of the template.
-
- 30 Sep, 2020 1 commit
-
-
stuartmorgan authored
-
- 25 Aug, 2020 1 commit
-
-
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
-
- 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
-
- 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.
-
- 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
-