Thank you @maxwhite / @defensivedepth for your replies. I am following the instructions at https://osquery.readthedocs.io/en/stable/development/windows-provisioning. According to the docs, you should not run tools\provision.ps1 directly. I ran tools\make-win64-dev-env.bat on both my laptop (Windows 10) and a Win2k16 server, then ran tools\make-win64-binaries.bat. On both my laptop, and the server their are test failures, but the Visual Studio 2015 project is built. I tried compiling the project using VS, and receive the error that benchmark.h is not found, so I added it from https://github.com/google/benchmark/tree/master/include/benchmark, but now I get an error that benchmark.lib is not found. I made the assumption that tools\make-win64-dev-env.bat just built the VS project and you had to compile the binaries from VS. Is tools\make-win64-dev-env.bat supposed to actually create the binaries?
08/23/2018, 3:15 PM
You can run provision.ps1 directly if you’d like, the .bat scripts just attempt to bypass execution policies. Sounds like you got your build figured out?