274 | | Tap-windows6 buildsystem runs code analysis automatically for x64 Release builds. Test analysis files are under directory ''tap-windows6\src\x64\Release'' named as ''<sourcefile>.nativecodeanalysis.xml''. Results of the code analysis are not enough, as you also need to [https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-log-file-for-static-driver-verifier Creating a log file for Static Driver Verifier]. |
| 274 | Tap-windows6 buildsystem runs code analysis automatically for x64 Release builds, so build that variant as the first step. Test analysis files are under directory ''tap-windows6\src\x64\Release'' named as ''<sourcefile>.nativecodeanalysis.xml''. Results of the code analysis are not enough, as you also need to [https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-log-file-for-static-driver-verifier Creating a log file for Static Driver Verifier]. |
| 275 | |
| 276 | Creating the Static Driver Verifier logs is a simple process once you know it. Launch a ''x64 Native Tools command prompt'' that comes with Visual Studio 2019. Then |
| 277 | |
| 278 | {{{ |
| 279 | PS> cd tap-windows6\src |
| 280 | PS> msbuild C:\users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj /p:Configuration=Release /p:Platform=x64 /target:sdv /p:inputs="/check" |
| 281 | }}} |
| 282 | |
| 283 | Note that you need to "cd" to the "src" directory. You also need to provide the full path to the vcxproj file. The SDV tests will take ''a lot'' of time so don't wait holding your breath. |
| 284 | |
| 285 | Once they pass you need to merge the results of SDV and codeanalysis. You can do this from Visual Studio 2019 from the "Extensions" -> "Driver" menu. |