notes2

https://www.crosswire.org/wiki/Tutorial:Compiling_%26_Installing_SWORD_on_Windows#Compiling_The_SWORD_Project_using_MS_Visual_Studio_2013
https://github.com/pbatard/libwdi/wiki/Signed-Driver-Walkthrough
http://www.windrvr.com/2015/05/11/wdk-installation-tips/
https://developer-content.emc.com/developer/devcon2004/downloads/PS_WDK_Developer_Tips_and_Tricks_Bluefish.pdf

https://msdn.microsoft.com/en-us/library/kezkeayy.aspx
https://msdn.microsoft.com/en-us/library/aa236630(v=vs.60).aspx
https://msdn.microsoft.com/en-us/library/xee0c8y7.aspx
https://msdn.microsoft.com/en-us/library/6y6t9esh.aspx


https://docs.microsoft.com/en-gb/windows-hardware/drivers/dashboard/update-a-code-signing-certificate
https://cmake.org/cmake/help/latest/variable/CMAKE_PREFIX_PATH.html
http://clang.llvm.org/docs/MSVCCompatibility.html
https://stackoverflow.com/questions/31915246/how-to-set-clang-cl-to-c14-or-c1z
https://ehsanakhgari.org/blog/2014-06-26/building-firefox-on-windows-with-clang-cl


EDIT: In another post on this same topic, it was mentioned that in order to pass arguments to clang itself when in clang-cl mode you must use:

-Xclang <arg>         Pass <arg> to the clang compiler

would be nice if you could update the build system with the next release (just the VS and WDK stuff)