/FS (Force Synchronous PDB Writes)
For the latest documentation on Visual Studio 2017 RC, see Visual Studio 2017 RC Documentation.
By default, when /Zi or /ZI is specified, the compiler locks PDB files to write type information and symbolic debugging information. This can significantly reduce the time it takes the compiler to generate type information when the number of types is large. If another process temporarily locks the PDB file—for example, an anti-virus program—writes by the compiler may fail and a fatal error may occur. This problem can also happen when multiple copies of cl.exe access the same PDB file—for example, if your solution has independent projects that use the same intermediate directories or output directories and parallel builds are enabled. The /FS compiler option prevents the compiler from locking the PDB file and forces writes to go through MSPDBSRV.EXE, which serializes access. This may make builds significantly longer, and it doesn't prevent all errors that may occur when multiple instances of cl.exe access the PDB file at the same time. We recommend that you change your solution so that independent projects write to separate intermediate and output locations, or that you make one of the projects dependent on the other to force serialized project builds.
The /MP option enables /FS by default.
Open the project's Property Pages dialog box. For details, see Working with Project Properties.
Select the C/C++ folder.
Select the Command Line property page.
Modify the Additional Options property to include
/FSand then choose OK.
- See AdditionalOptions.