Joerg Sonnenberger 399aea300f 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 llvm-svn: 288436		2016-12-01 23:37:45 +00:00
..
Core	Do not do raw name replacement when FromDecl is a class forward-declaration.	2016-11-25 16:02:49 +00:00
ArgumentsAdjusters.cpp	Typo.	2016-11-25 20:15:57 +00:00
CMakeLists.txt	clangTooling: Update libdeps: LLVMOptions, since r280118.	2016-08-31 00:46:32 +00:00
CommonOptionsParser.cpp	Apply some suggestions from clang-tidy's performance-unnecessary-value-param.	2016-06-15 14:20:56 +00:00
CompilationDatabase.cpp	Extend CompilationDatabase by a field for the output filename	2016-12-01 23:37:45 +00:00
FileMatchTrie.cpp	Tooling: Hide implementation details	2015-03-09 15:03:26 +00:00
FixIt.cpp	[tooling] FixItHint Tooling refactoring	2016-05-11 14:31:39 +00:00
JSONCompilationDatabase.cpp	Extend CompilationDatabase by a field for the output filename	2016-12-01 23:37:45 +00:00
Refactoring.cpp	Deduplicate replacements by FileEntry instead of file names.	2016-11-07 06:08:23 +00:00
RefactoringCallbacks.cpp	Implement tooling::Replacements as a class.	2016-08-01 10:16:37 +00:00
Tooling.cpp	Fix memory leak by storing returned pointer in std::unique_ptr	2016-08-30 21:12:48 +00:00