[cfe-dev] Clang Tools

[Manuel Klimek]

On Mon, Jan 21, 2013 at 8:31 AM, madil90 <madil90 at gmail.com> wrote:

> Hi,
>    I had a standalone clang program which I am trying to convert to a clang
> tool. My basic requirement is that my tool should be able to find all
> default c++ paths and that it's build should be kept separate from the
> clang
> source. How can I do this? I tried using the .json file approach but that
> does not enable to build my tool separately from clang. Please guide me on
> how to write an independent tool (just give the steps. I will figure the
> rest out) that can easily find all c++ header files.
>

Hi Adil,

I'm not sure what you're looking for - that is, I don't understand what
your exact requirements are, and why the .json compilation database didn't
work for you. What exactly do you mean with "build separately from clang".
And why's that a requirement?

Cheers,
/Manuel


>
> Regards,
> Adil
>
>
>
> --
> View this message in context:
> http://clang-developers.42468.n3.nabble.com/Clang-Tools-tp4029913.html
> Sent from the Clang Developers mailing list archive at Nabble.com.
> _______________________________________________
> 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/20130121/89dd1b6b/attachment.html>