Using a build trace to troubleshoot build specification problems
You can use kwinject to generate a build trace, a file that contains the sequence of process calls that took place during your C/C++ build.
A build trace can be useful for:
- determining the exact name of your compiler. kwinject needs to know the exact name of your compiler so that it can capture your build settings.
- diagnosing problems with your build specification, such as missing files, missing includes, or a build specification that contains only a version line.