1. 02 Oct, 2019 1 commit
  2. 27 Sep, 2019 1 commit
  3. 11 Sep, 2019 1 commit
    • stuartmorgan's avatar
      Add an ephemeral directory to Windows projects (#40194) · e6ae95c4
      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.
      e6ae95c4
  4. 02 Sep, 2019 1 commit
  5. 21 Aug, 2019 1 commit
    • stuartmorgan's avatar
      Add build warning for non-debug desktop builds (#38932) · 01530928
      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.
      01530928
  6. 22 Jul, 2019 3 commits
  7. 13 Jul, 2019 1 commit
  8. 01 Jul, 2019 1 commit
  9. 10 Jun, 2019 3 commits
  10. 06 Jun, 2019 1 commit
    • stuartmorgan's avatar
      Add 'doctor' support for Windows (#33872) · fb8df82c
      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.
      fb8df82c
  11. 29 May, 2019 3 commits
    • stuartmorgan's avatar
      Build the solution on Windows (#33528) · 79ae04d4
      stuartmorgan authored
      Switch from building Runner.vcxproj to Runner.sln on Windows, to allow
      for multiple-project builds (e.g., separate plugin projects).
      79ae04d4
    • stuartmorgan's avatar
      Use vswhere to find Visual Studio (#33448) · aecf053e
      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
      aecf053e
    • stuartmorgan's avatar
      Wrap Windows build invocation in a batch script (#33443) · e1a784ae
      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
      e1a784ae
  12. 14 May, 2019 1 commit
    • stuartmorgan's avatar
      Teach flutter msbuild for Windows (#32335) · 6722fb44
      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.
      6722fb44
  13. 29 Apr, 2019 1 commit
  14. 18 Apr, 2019 1 commit
  15. 17 Apr, 2019 1 commit