microsoft / microsoft/ebpf-for-windows
Failure to build after using Setup-DevEnv.ps1
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 311
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 21
Description
jsturtevant posted the following on the ebpf-for-windows slack channel:
```I've followed the instructions at https://github.com/microsoft/ebpf-for-windows/blob/main/docs/GettingStarted.md#building-ebpf-for-windows and can't seem to get the project to build I have multiple errors like:
"C:\Users\azureuser\ebpf-for-windows\ebpf-for-windows.sln" (default target) (1) ->
"C:\Users\azureuser\ebpf-for-windows\netebpfext\netebpfext.vcxproj.metaproj" (default target) (12) ->
"C:\Users\azureuser\ebpf-for-windows\netebpfext\netebpfext.vcxproj" (default target) (23) ->
(PrepareForBuild target) ->
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Microsoft\VC\v160\Microsoft.CppBuild.targets(439,5): error MSB8020: The build tools for WindowsKernelModeDriver10.0 (Platform Toolset = 'WindowsKernelModeDr
iver10.0') cannot be found. To build using the WindowsKernelModeDriver10.0 build tools, please install WindowsKernelModeDriver10.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the P
roject menu or right-click the solution, and then selecting "Retarget solution". [C:\Users\azureuser\ebpf-for-windows\netebpfext\netebpfext.vcxproj]
I think i have this installed (I used the script at https://github.com/microsoft/ebpf-for-windows/blob/main/scripts/Setup-DevEnv.ps1) and see on the machine. I've also tried doing the "retarget solution" in VS with no luck
What am I missing? I am running on Windows 11 if that makes a difference```
Contributor guide
Research direction
Read docs/GettingStarted.md at the build section and scripts/Setup-DevEnv.ps1, then inspect ebpf-for-windows.sln and netebpfext/netebpfext.vcxproj around the WindowsKernelModeDriver10.0 toolset reference. Reproduce the build on Windows 11 and compare the script's installed components with the project's required toolset; done means the documented setup builds the solution without MSB8020.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, powershell
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100