As discussed on #12903:
Context
Alpha/PR builds were suddenly failing due to the symbol store failing to build.
Example: https://ci.appveyor.com/project/NVAccess/nvda/builds/40999821
Issue
As discussed on https://github.com/MicrosoftDocs/windows-driver-docs/issues/2931#event-5422267809,
the documentation for symstore.exe usage was somewhat inconsistent. The following has been clarified:
I updated the topic to mention that NOREFS is used with the /p option for pointer file creation. And you may be aware, but compress is not used with pointer files, so /p and /compress would not be used together. I also added the ZIP|CAB option for compress that is shown in the command line help.
I should mention, that for other information on the use of symbols, there is also a discussion area that driver developers use to figure out challenging issues with building code. Hardware and Application Developers on Q&A. You can post your question there, and the community of developers usually give feedback fairly quickly. Good luck with your use of the symstore command in your build process.
While builds are working now, our usage is still not inline with the documentation.
Potential solution
Update buildSymbolStore.ps1 symstore.exe usage to be inline with documentation. Test with an AppVeyor build to compare symbol stores.
As discussed on #12903:
Context
Alpha/PR builds were suddenly failing due to the symbol store failing to build.
Example: https://ci.appveyor.com/project/NVAccess/nvda/builds/40999821
Issue
As discussed on https://github.com/MicrosoftDocs/windows-driver-docs/issues/2931#event-5422267809,
the documentation for
symstore.exeusage was somewhat inconsistent. The following has been clarified:While builds are working now, our usage is still not inline with the documentation.
Potential solution
Update
buildSymbolStore.ps1symstore.exe usage to be inline with documentation. Test with an AppVeyor build to compare symbol stores.