Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

we’ve had to comment out the doxygen part of the powershell build script

And is everything else normal (the NuGet and psscriptanalyzer)? Since I get an error when I try to use make-win64-binaries.bat

Still not working :disappointed:
this is the log I'm getting when running make-win64-binaries.bat
```.\tools\make-win64-binaries.bat : CMake Error: The source directory "C:/Users/Administrator/osquery" does not appear to 
contain CMakeLists.txt.
At line:1 char:1
+ .\tools\make-win64-binaries.bat
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (CMake Error: Th...CMakeLists.txt.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
Specify --help for usage, or press the help button on the CMake GUI.
Microsoft (R) Build Engine version 15.9.21+g9802d43bc3 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

MSBUILD : error MSB1009: Project file does not exist.
Switch: osquery.sln

[-] osquery build failed.```

did you run `.\tools\make-win64-dev-env.bat` first?

when I run `make-win64-binaries` under a VS command prompt I get `[-] Failed to find vs build tools. Re-run tools\make-win64-dev-env.bat`

using vs 2017 (with an chocolatey installation of build tools) but also installed vs 2015 build tools by mistake

I just run a command prompt as administrator, then run the `.\tools\make-win64-dev-env.bat` to get all the required packages from chocolatey. that usually does the trick

you might want to make sure that chocolatey’s binary folder is added to your path

```C:\ProgramData\chocolatey\bin``` should be somewhere in your `PATH` environment variable.

Did that multiple times as well... haven’t checked the path thing but do you think it’s related to the vs build tools or the CMakeLists.txt problems?

yeah. chocolatey installs vs build tools itself. so even if you don’t have visual studio installed on your machine, running `.\tools\make-win64-dev-env.bat` will install vs build tools

but it installs them to `C:\ProgramData\chocolately\bin`

for example, on my machine, I run a command prompt as administrator and then type `where cl` and it returns this: ```&gt; where cl
C:\ProgramData\chocolatey\bin\cl.exe```

Will check that today and get back to you

Is there anything else you think could be it?

nothing else I can think of. you might want to clone the repo somewhere else and try again