1. 25 Jan, 2019 1 commit
    • Jose Fonseca's avatar
      appveyor: Revert commits adding Cygwin support. · 65b8d723
      Jose Fonseca authored
      This reverts commits 00ad77b9 and
      5334dafe.
      
      This avoids Appveyor build breakage due to Cygwin, but more importantly,
      there are several problems with these patches, as highlighted to my
      recent mesa-dev mail.  So better to revert for now, and pursue Cygwin
      support after these have been address.
      65b8d723
  2. 07 Jan, 2019 2 commits
  3. 16 Oct, 2018 3 commits
  4. 21 Aug, 2018 1 commit
  5. 16 Jun, 2018 1 commit
  6. 22 Feb, 2018 1 commit
  7. 29 Mar, 2017 1 commit
  8. 13 Sep, 2016 1 commit
  9. 11 Aug, 2016 2 commits
  10. 14 Apr, 2016 1 commit
  11. 03 Feb, 2016 1 commit
  12. 08 Dec, 2015 1 commit
    • Jose Fonseca's avatar
      appveyor: Cache winflexbison archive. · a9a0c693
      Jose Fonseca authored
      Unforunately the Appveyor -> SourceForge connection seems a bit
      unreliable, causing frequent build failures while downloading
      winflexbison (approx once every 2 days).
      
      Fetching winflexbison archive into Appveyor's cache should eliminate
      these.
      
      Fetching Python modules from PyPI doesn't seem to be a problem, so they
      are left alone for now, though they could eventually get the same
      treatment.
      a9a0c693
  13. 02 Dec, 2015 1 commit
    • Jose Fonseca's avatar
      appveyor: Initial integration. · 9e6af566
      Jose Fonseca authored
      AppVeyor doesn't require an appveyor.yml in the repos (in fact it has
      some limitations as noted in comments below), but doing so has two great
      advantages over the web UI:
      
      - appveyor.yml can be revisioned together with the code, so instructions
        should always be in synch with the code
      
      - appveyor.yml can be reused for people's private repositories (be on
        fdo or GitHub, etc.)
      Acked-by: 's avatarRoland Scheidegger <sroland@vmware.com>
      9e6af566