- 02 Oct, 2019 1 commit
-
-
Ian Hickson authored
-
- 27 Sep, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 11 Sep, 2019 1 commit
-
-
stuartmorgan authored
Moves files generated in windows/flutter/ as part of the build to an ephemeral/ subdirectory, matching the approach used on macOS (and in the future, Windows). Adds that directory to the generated properties file to minimize hard-coding of paths in the project.
-
- 02 Sep, 2019 1 commit
-
-
Jonah Williams authored
-
- 21 Aug, 2019 1 commit
-
-
stuartmorgan authored
When building in profile or release mode on desktop, add a prominent warning that it's actually a debug build. This is to help address issues with people being unaware of the current state of builds due to following third-party guides rather than official documentation. macOS is not included since PRs are in flight for macOS release support.
-
- 22 Jul, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
This reverts commit bd52a78c.
-
Jonah Williams authored
-
- 13 Jul, 2019 1 commit
-
-
Ian Hickson authored
Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108)
-
- 01 Jul, 2019 1 commit
-
-
stuartmorgan authored
- Adds desktop projects to ApplicationPackageStore - Plumbs target overrides through the desktop builds
-
- 10 Jun, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
-
Jonah Williams authored
-
- 06 Jun, 2019 1 commit
-
-
stuartmorgan authored
Moves the logic for finding vcvars64.bat to a new VisualStudio class that encapsulates finding, and providing information about, VisualStudio installations. Adds a validator for it, and runs it for Windows workflows in doctor.
-
- 29 May, 2019 3 commits
-
-
stuartmorgan authored
Switch from building Runner.vcxproj to Runner.sln on Windows, to allow for multiple-project builds (e.g., separate plugin projects).
-
stuartmorgan authored
Rather than hard-coding a set of locations to check, use vswhere (which is installed by VS 2017 and later), and construct the vcvars64.bat path relative to that. This will allow Windows builds to work without special configuration for people who have VS installed at a custom path. Also adds error logging with different messages for each failure point, so that rather than the not-very-informative 'failed to find vcvars64.bat' message, the failure will provide feedback about what to do. This is an interim solution; later this will be replaced by a VisualStudio class with associated validator to match the structure of the other toolchains. Fixes #33249
-
stuartmorgan authored
Invoking msbuild with runInShell makes handling path escaping more error-prone, and substantially increases the chances of running into maximum path limits. This replaces the direct call with a .bat wrapper that calls vsvars64.bat then msbuild, and uses relative paths within the script to keep command lengths short. Fixes https://github.com/flutter/flutter/issues/32792
-
- 14 May, 2019 1 commit
-
-
stuartmorgan authored
Eliminates the need for a build.bat in the Windows build workflow, adding preliminary support for building using msbuild. The handling of vcvars64.bat may be refined in the future, but this serves as a starting point.
-
- 29 Apr, 2019 1 commit
-
-
Dan Field authored
* Re-enable const
-
- 18 Apr, 2019 1 commit
-
-
Jonah Williams authored
-
- 17 Apr, 2019 1 commit
-
-
Jonah Williams authored
-