[cfe-dev] compile_commands.json for Windows/MSVC

[Chandler Carruth]

On Wed, Aug 14, 2013 at 1:57 AM, Kim Gräsman <kim.grasman at gmail.com> wrote:

> > As an alternative, you could add direct support to the tooling library
> for
> > querying Visual Studio for the commandline if there is a reasonable IPC
> > mechanism for doing that.
> >
> > As another alternative, you could add a plugin to Visual Studio that
> caused
> > it to write out the json database whenever the project settings
> changed...
> > If there is a reasonable plugin layer to do that.
>
> I'd prefer to parse the VS project files and spit out a compilation
> database. They are plain XML and as of VS2010 (I think) supposed to be
> backward compatible, so it's a stable format.


My problem with this is that it adds an extra step every time the project
file changes. If you forget it, your tool begins to misbehave in
potentially surprising ways.

Maybe you could make the logic involve parsing and spitting out, but
embedding it into a plugin that gets notified when VS sees the project file
change? (I clearly have no idea how this stuff works...)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130814/8273fc7f/attachment.html>