Manuel Klimek klimek at google.com
Thu Jun 21 01:07:31 PDT 2012

On Wed, Jun 20, 2012 at 9:59 PM, Bertjan Broeksema <broeksema at kde.org>wrote:

> 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.

The reason why you might want a slightly diffferent file format is the key.
For the compilation database, the usual question is "how do I parse this
TU?". What would you key on for link commands? The output file?


> Cheers,
> Bertjan
> == 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
> rather,
> 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
> get
> included, b) I get some pointers on where to start to make it happen.
> Cheers,
> Bertjan
> [1] https://gitorious.org/cpp-dependency-analyzer/cpp-dependency-analyzer
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20120621/e0bc6fe6/attachment.html>

More information about the cfe-dev mailing list