Add Compilation Database to handle different configuration sources in an unique way

[guwirth]

At the moment we have different solution to handle macros and include directories from different sources:

• config file
• Visual Studio LOG file
• JsonCompilationDatabase

Would be the best to have only one internal handling for this:

• read the source only once, store result in CxxConfiguration
• Visual Studio LOG file: reading the configuration should be separated from other functionality. At the moment reading issues and settings is mixed behind one config value.

Proposal:

• create a database (map) in CxxConfiguration
• should be possible to define global settings (valid for all files)
• should be possible to define source file specific macros and includes
  • key is the source file name
  • values are:
    • file specific include paths
    • file specific macros
• different config sources should use this one DB as backend
• config file should be read only once

see also #1325, #1326,

[Bertk]

Hi @guwirth,

will this proposal also support C++ Modules?

Visual Studio supports definitions for VS C++ projects and for C++ implementation files. As far as I know does the C++ Community plug-in not supports all of this levels. Will this proposal consider the definitions on file level?

Best regards
Bert

[guwirth]

Hi @Bertk,

in C++ typically only the C or C++ files are compiled (and the header files only indirect). So it should be sufficient to create a database with c/cpp files and the related macros and includes per file?

Regards,
Günter