sakerbuild / saker.msvc Goto Github PK

The debugging information generation and usage should be supported. However, multiple aspects should be examined:

• How the embedded paths in object files related to the build system.
  • They are probably absolute, yet the build system uses its own path configuration.
  • How moving the object files may affect the results?
• How can we handle PDBs.
• How distributed compilation affects debugging information.
  • Can the PDBs be moved between build machines and then merged?
    • Can embedded paths break this moving between machines?

Related links:

• /PDBALTPATH
• /d1trimfile
• /Z7, /Zi, /ZI (Debug Information Format)
• /Fd (Program Database File Name)
• /FS (Force Synchronous PDB Writes)
• /DEBUG

Support creating and consuming precompiled headers with the build tasks.

The distributed compilation performance results at https://saker.build/saker.msvc/doc/performancecomparison.html is not what we would expect. The measurements are compared to IncrediBuild which is an already established tool, however, it seems to perform significantly worse than saker.build.

• Discuss possible misconfigurations of IncrediBuild that could've lead to performance degradation.
• Perform the measurements on more than 2 computers. (Possibly using the cloud if no direct hardware is available.)

Support compiling and consuming modules.

Solving the issue requires a stable command line API of the cl.exe tool. (Using experimental MSVC versions may be buggy, prone to breakage, and undocumented, making implementation harder.)