Bertjan Broeksema broeksema at kde.org
Wed Jun 20 12:59:00 PDT 2012

Hi List,

Crossposting from cmake.devel. I found out that a particular feature in 
CMake was contributed by the clang community. I'm working on a small tool 
which requires the same information + some additional. That is, in its 
currents form it only stores the compile commands and not the link commands. 
Is this something the clang community would be interested in too (for 
tooling at the link level, if such is planned)?

The question would be if the link commands would be stored in the same file, 
resulting in a "build database" in stead of a compile database or in a 
separate file. Any input on this topic is welcome.



== Original message ==

I recently found out about the CMAKE_EXPORT_COMPILE_COMMANDS option while 
getting myself familiar with clang. In a tool [1] I'm working on (or 
start to work again) I need something similar.

The current CMAKE_EXPORT_COMPILE_COMMANDS option only exports compile 
commands (as its name suggest). However, in my tool I build and visualize 
the full graph (i.e. source, headers, objectfiles, libaries). For this I 
also would need the link commands. Currently I've a wrapper around the C++ 
compiler, which works fine, but after having seen this option I realized 
that this would be way more convenient. Is it possible to get a similar 
option for exporting link commands or perhaps both:


I'm willing to work on a patch, given that a) the option has a change to 
included, b) I get some pointers on where to start to make it happen.



[1] https://gitorious.org/cpp-dependency-analyzer/cpp-dependency-analyzer

More information about the cfe-dev mailing list