[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cfe-dev
Subject:    Re: [cfe-dev] Standalone tools
From:       Jacob Carlborg <doob () me ! com>
Date:       2014-04-27 14:09:18
Message-ID: ljj32e$qvv$1 () ger ! gmane ! org
[Download RAW message or body]

On 2014-04-26 23:11, Kim Gr=E4sman wrote:
> Hi all,
>
> I'm one of the maintainers of IWYU, a tool for cleaning up #include
> dependencies.
>
> We've experimented with releasing IWYU binaries for a select number of
> platforms, but people are having problems because Clang is looking for
> headers relative to the executable. There have been reports that
> moving IWYU into the Clang install directory makes things work, but
> this is intrusive and a number of users don't even have Clang
> installed.
>
> Is there a strategy for how to package up a standalone Clang tool so
> it can be distributed? Do/can we include the headers from
> ...lib/clang/3.5.0/include? Anything else necessary?

I'm having the same problem. Currently I'm telling my users to =

separately install Clang. For the include files, it also work to copy =

them to the standard header locations.

It would be nice if the header files could be embedded in the tool (the =

executable).

-- =

/Jacob Carlborg

_______________________________________________
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]