1 # http://www.appveyor.com/docs/appveyor-yml
3 # To setup AppVeyor for your own personal repositories do the following:
6 # - Select Git and fill in the Git clone URL
7 # - Setup a Git hook as explained in
8 # https://github.com/appveyor/webhooks#installing-git-hook
9 # - Check 'Settings > General > Skip branches without appveyor.yml'
10 # - Check 'Settings > General > Rolling builds'
11 # - Setup the global or project notifications to your liking
13 # Note that kicking (or restarting) a build via the web UI will not work, as it
14 # will fail to find appveyor.yml . The Git hook is the most practical way to
18 # - http://help.appveyor.com/discussions/problems/2209-node-grunt-build-specify-a-project-or-solution-file-the-directory-does-not-contain-a-project-or-solution-file
19 # - http://help.appveyor.com/discussions/questions/1184-build-config-vs-appveyoryaml
27 # Don't download the full Mesa history to speed up cloning. However the clone
28 # depth must not be too small, otherwise builds might fail when lots of patches
29 # are committed in succession, because the desired commit is not found on the
33 # - https://www.appveyor.com/blog/2014/06/04/shallow-clone-for-git-repositories
36 # https://www.appveyor.com/docs/build-cache/
38 - '%LOCALAPPDATA%\pip\Cache -> appveyor.yml'
39 - win_flex_bison-2.5.15.zip
40 - llvm-5.0.1-msvc2017-mtd.7z
41 - subprojects\packagecache -> subprojects\*.wrap
43 os: Visual Studio 2019
46 # Appveyor defaults core.autocrlf to input instead of the default (true), but
47 # that can hide problems processing CRLF text on Windows
48 - git config --global core.autocrlf true
51 Path: C:\Python38-x64;C:\Python38-x64\Scripts;%Path%
52 WINFLEXBISON_VERSION: 2.5.15
53 LLVM_ARCHIVE: llvm-5.0.1-msvc2017-mtd.7z
59 - cmd: .appveyor\appveyor_msvc.bat install
62 - cmd: .appveyor\appveyor_msvc.bat build_script
65 - cmd: .appveyor\appveyor_msvc.bat test_script
67 # It's possible to setup notification here, as described in
68 # http://www.appveyor.com/docs/notifications#appveyor-yml-configuration , but
69 # doing so would cause the notification settings to be replicated across all
70 # repos, which is most likely undesired. So it's better to rely on the
71 # Appveyor global/project notification settings.