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

List:       cfe-dev
Subject:    Re: [cfe-dev] Standalone tools
From:       Kim Gräsman <kim.grasman () gmail ! com>
Date:       2014-04-28 6:18:47
Message-ID: CANt7B+czmuL+09yvD+o5Gb0GVQyu81r=V3b+EcVHqpeMoV33KA () mail ! gmail ! com
[Download RAW message or body]

Sorry, I lost the list in my reply, adding it back here.

On Mon, Apr 28, 2014 at 8:08 AM, Dmitri Gribenko <gribozavr@gmail.com> wrote:
> On Mon, Apr 28, 2014 at 6:41 AM, Kim Gräsman <kim.grasman@gmail.com> wrote:
>> Hi Dmitri,
>>
>> 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.
>>
>> That occurred to me too when I saw Jacob's comment.
>>
>> I'm not intimately familiar with the VFS implementation (I've only
>> seen the patches whizzing by on cfe-commits); do you think it would be
>> "not hard" to mix different VFS implementations in header search? I
>> guess every include path entry would need to be served by a different
>> VFS.
>
> I think existing implementation should be almost good enough -- just
> add a feature to read file contents from a YAML key, and stuff the
> contents of the headers into the YAML file.

Thanks, I'll see if I can get my head around it!

- Kim

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