]> granicus.if.org Git - clang/commit
Extend CompilationDatabase by a field for the output filename
authorJoerg Sonnenberger <joerg@bec.de>
Thu, 1 Dec 2016 23:37:45 +0000 (23:37 +0000)
committerJoerg Sonnenberger <joerg@bec.de>
Thu, 1 Dec 2016 23:37:45 +0000 (23:37 +0000)
commit5ca7f4286d20192dff833f91865b10be0debd76d
tree0de09621560e788db5ce1b214a8d70f7a24088b4
parentbef1cdf7e4d1e313f0f8b4acff0b0ad4c1e03d6c
Extend CompilationDatabase by a field for the output filename

In bigger projects like an Operating System, the same source code is
often compiled in slightly different ways. This could be the difference
between PIC and non-PIC code for static vs dynamic libraries, it could
also be the difference between size optimised versions of tools for
ramdisk images. At the moment, the compilation database has no way to
distinguish such cases. As first step, add a field in the JSON format
for it and process it accordingly.

Differential Revision: https://reviews.llvm.org/D27138

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@288436 91177308-0d34-0410-b5e6-96231b3b80d8
docs/JSONCompilationDatabase.rst
include/clang/Tooling/CompilationDatabase.h
include/clang/Tooling/JSONCompilationDatabase.h
lib/Tooling/CompilationDatabase.cpp
lib/Tooling/JSONCompilationDatabase.cpp
unittests/Tooling/CompilationDatabaseTest.cpp