From e0a41a85fc269b6e8b2ac19f9d09858d09a7557c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nicolas=20L=C3=A9veill=C3=A9?= <nicolas@uucidl.com>
Date: Sun, 20 Sep 2015 17:16:43 +0200
Subject: [PATCH] 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
---
 appveyor.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/appveyor.yml b/appveyor.yml
index 2aef9c9..428d656 100644
--- a/appveyor.yml
+++ b/appveyor.yml
@@ -12,6 +12,7 @@ build_script:
     } 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
-- 
GitLab