hammer/appveyor.yml
Nicolas Léveillé e0a41a85fc Add workaround for VS2015 so that appveyor works
It seems Appveyor's images have been changed. The builds could not
find standard library headers anymore.

It seems to be an interaction between MS' scripts and the Windows
Driver Kit that is installed there.

One way to disable this interaction is to rename the `wdf` folder to
some other name.

See:
- http://stackoverflow.com/questions/31862627/vs2015-cl-cant-find-crt-libs-stido-h-ctype-h-etc-when-building-on-command-l
- http://help.appveyor.com/discussions/problems/3062-problem-with-new-updates-visual-studio-2015-and-cmake
- https://github.com/appveyor/ci/issues/414
2015-09-20 17:16:43 +02:00

20 lines
511 B
YAML

platform:
- x86
- x64
version: 1.0.{build}
os: Visual Studio 2015
build_script:
- '@echo off'
- setlocal
- ps: >-
If ($env:Platform -Match "x86") {
$env:VCVARS_PLATFORM="x86"
} Else {
$env:VCVARS_PLATFORM="amd64"
}
ren 'C:\Program Files (x86)\Windows Kits\10\include\wdf' '00wdf'
- call "%VS140COMNTOOLS%\..\..\VC\vcvarsall.bat" %VCVARS_PLATFORM%
- call tools\windows\build.bat
# FIXME(windows) TODO(uucidl): reactivate examples
# - call tools\windows\build_examples.bat
- exit /b 0