ARM Compiler options listed in both the console window and the build log record the extension for preprocessor dependency files as '.d_raw':
--preproc_dependency="filename.d_raw"
I have been unable to find any reference to the use of '.d_raw' in TI documentation.
As I anticipated, the resulting dependency files are created with the '.d' extension.
I attempted to use the Parser Preprocessing Options to force the entries in the console window and build log to be consistent with the files created.
I changed the mode from “automatic (default)” to manual, selected “–preproc_with_compile” and specified ${InputFileBaseName}.d for the dependency filename.
This appeared to work as I expected. All dependency files were created with the '.d' extension and the preprocessor dependency was reported as --preproc_dependency="filename.d" in the console window and build log.
The problem with this approach is Code Composer Studio issues a warning with the following description:
This project is currently in 'manual' Parser Preprocessing mode - no dependency graph is automatically generated.
This mode should only be temporarily used to generate various pre-processor listing files.
Please switch the Parser Preprocessing mode back to 'automatic' for you regular builds.
Obviously, I am reluctant to use options which CCS is warning against.
Therefore, I will probably have to revert to using the ’ automatic (default)’ Parser Preprocessing mode.
I would like to be able to refer to a TI document which details precisely what is expected when using the ’ automatic (default)’ Parser Preprocessing mode.
In particular, it would be useful if you could point me at a specific mention of '.d_raw'.