[prev in list] [next in list] [prev in thread] [next in thread]
List: cfe-dev
Subject: Re: [cfe-dev] Standalone tools
From: Manuel Klimek <klimek () google ! com>
Date: 2014-04-28 16:53:46
Message-ID: CAOsfVvnrgFjvEb8gZCSU9VVN6JY-QdmV2A7pZycgv-+4hJ7_MA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Apr 28, 2014 at 7:35 AM, Kim Gr=C3=A4sman <kim.grasman@gmail.com> w=
rote:
> Hi Jacob,
>
> On Sun, Apr 27, 2014 at 4:09 PM, Jacob Carlborg <doob@me.com> wrote:
> >
> > I'm having the same problem. Currently I'm telling my users to separate=
ly
> > install Clang.
>
> Do you deploy to Unix-like systems only? I'm guessing this works well
> there, because everything is rooted in /usr/bin, right?
>
Btw, this is not the recommended way - the recommended way is to ship the
builtin headers with the tool (the builtin headers are basically versioned
with the parser).
>
> So:
>
> /usr/bin/your-tool
> /usr/bin/clang
> /usr/lib/clang/3.5.0/include
>
> ?
>
> On Windows, the situation is a little different as everything installs
> into C:\Program Files\LLVM, including the headers. So the only way to
> have a tool find the headers would be to install it into LLVM's root
> directory, which seems a little intrusive...
>
> > For the include files, it also work to copy them to the
> > standard header locations.
>
> You mean the equivalent of /usr/lib/clang/3.5.0/include? If Clang was
> installed afterwards, wouldn't they conflict?
>
> > It would be nice if the header files could be embedded in the tool (the
> > executable).
>
> That sounds like a lovely idea.
>
> The only obvious way I can see, given the current state, to achieve
> some kind of isolation is to:
> - install IWYU into /usr/bin/include-what-you-use
> - install Clang headers into
> /usr/lib/include-what-you-use/<version>/include
>
> For Windows, replace "/usr" with some install directory, e.g.
> "C:\Program Files\IWYU"
>
> This is assuming the headers is the only thing I need to worry about,
> but for a syntax-only tool, it should be, right?
>
> Thanks,
> - Kim
> _______________________________________________
> cfe-dev mailing list
> cfe-dev@cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Apr 28, 2014 \
at 7:35 AM, Kim Gräsman <span dir="ltr"><<a href="mailto:kim.grasman@gmail.com" \
target="_blank">kim.grasman@gmail.com</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi Jacob,<br> <div class=""><br>
On Sun, Apr 27, 2014 at 4:09 PM, Jacob Carlborg <<a \
href="mailto:doob@me.com">doob@me.com</a>> wrote:<br> ><br>
</div><div class="">> I'm having the same problem. Currently I'm telling \
my users to separately<br> > install Clang.<br>
<br>
</div>Do you deploy to Unix-like systems only? I'm guessing this works well<br>
there, because everything is rooted in /usr/bin, \
right?<br></blockquote><div><br></div><div>Btw, this is not the recommended way - the \
recommended way is to ship the builtin headers with the tool (the builtin headers are \
basically versioned with the parser).</div> <div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <br>
So:<br>
<br>
/usr/bin/your-tool<br>
/usr/bin/clang<br>
/usr/lib/clang/3.5.0/include<br>
<br>
?<br>
<br>
On Windows, the situation is a little different as everything installs<br>
into C:\Program Files\LLVM, including the headers. So the only way to<br>
have a tool find the headers would be to install it into LLVM's root<br>
directory, which seems a little intrusive...<br>
<div class=""><br>
> For the include files, it also work to copy them to the<br>
> standard header locations.<br>
<br>
</div>You mean the equivalent of /usr/lib/clang/3.5.0/include? If Clang was<br>
installed afterwards, wouldn't they conflict?<br>
<div class=""><br>
> It would be nice if the header files could be embedded in the tool (the<br>
> executable).<br>
<br>
</div>That sounds like a lovely idea.<br>
<br>
The only obvious way I can see, given the current state, to achieve<br>
some kind of isolation is to:<br>
- install IWYU into /usr/bin/include-what-you-use<br>
- install Clang headers into \
/usr/lib/include-what-you-use/<version>/include<br> <br>
For Windows, replace "/usr" with some install directory, e.g.<br>
"C:\Program Files\IWYU"<br>
<br>
This is assuming the headers is the only thing I need to worry about,<br>
but for a syntax-only tool, it should be, right?<br>
<br>
Thanks,<br>
- Kim<br>
<div class="HOEnZb"><div \
class="h5">_______________________________________________<br> cfe-dev mailing \
list<br> <a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" \
target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br> \
</div></div></blockquote></div><br></div></div>
_______________________________________________
cfe-dev mailing list
cfe-dev@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic