[cfe-commits] r113817 - in /cfe/trunk: ./ examples/PrintFunctionNames/ examples/clang-interpreter/ examples/wpa/ lib/AST/ lib/Analysis/ lib/Basic/ lib/Checker/ lib/CodeGen/ lib/Driver/ lib/Frontend/ lib/FrontendTool/ lib/Index/ lib/Lex/ lib/Parse/ lib/Rewrite/ lib/Sema/ lib/Serialization/ tools/c-index-test/ tools/driver/ tools/libclang/

[Douglas Gregor]

On Sep 21, 2010, at 1:56 PM, Jason Haslam wrote:

> On Sep 21, 2010, at 2:40 PM, Douglas Gregor wrote:
> 
>> On Sep 21, 2010, at 1:25 PM, Jason Haslam wrote:
>> 
>>> Hello, 
>>> 
>>> Why was this patch reverted? Using the CMake dependency tracking for libraries makes it a lot easier to integrate clang into other CMake-based build systems. If there's something that can be done to fix the patch I'd be willing to work on it.
>> 
>> The dependencies are still available in LLVMLibDeps.cmake, which is to be semi-automatically updated as library dependencies change. So CMake already has all of the dependencies; they're just not explicit in each CMakeLists.txt.
> 
> Is there something similar for Clang? For example, I'm trying to get a list of libraries (in correct order for some linkers) that are needed to link clangAST. For now we're just deriving the list through trial-and-error, but seeing these checkins gave me hope that there might be an easier way.

Clang has explicit dependencies in the CMakeLists.txt. I'm hoping we'll get a ClangLibDeps.cmake, maintained the same was as LLVMLibDeps.cmake.

	- Doug