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

List:       cfe-dev
Subject:    Re: [cfe-dev] Standalone tools
From:       Tobias Grosser <tobias () grosser ! es>
Date:       2014-04-28 17:17:14
Message-ID: 535E8D1A.8080603 () grosser ! es
[Download RAW message or body]

On 28/04/2014 18:56, Manuel Klimek wrote:
> On Mon, Apr 28, 2014 at 6:54 PM, Dmitri Gribenko <gribozavr@gmail.com>wrote:
>
>> On Mon, Apr 28, 2014 at 5:52 PM, Manuel Klimek <klimek@google.com> wrote:
>>> On Sun, Apr 27, 2014 at 4:31 PM, Dmitri Gribenko <gribozavr@gmail.com>
>>> wrote:
>>>>
>>>> On Sun, Apr 27, 2014 at 3:09 PM, Jacob Carlborg <doob@me.com> wrote:
>>>>> It would be nice if the header files could be embedded in the tool
>> (the
>>>>> executable).
>>>>
>>>> Now that Clang has a VFS, this should not be hard to implement.
>>>
>>> Note that I have suggested this before (multiple times), and the powers
>> that
>>> are (well, Chandler & Doug) have shot down the idea.
>>
>> I am not judging whether it is good or not.  It just became easier than
>> ever.
>>
>
> Oh, it was always easy - the Tooling stuff always had access to the VFS
> layer that has been there forever. Chandler objected on a principled basis
> (how do we show error message that reference files that are not on disk,
> among others)

FYI, for tools like clang_complete finding these headers causes 
regularly issues when file system paths change and YCM just includes 
some version of the headers in its own code, which seems to work but is 
to my understanding incorrect. So having those headers readily available 
seems from a user's perspective a good thing.

Cheers,
Tobias
_______________________________________________
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]