[Rock-dev] clang vs. typelib

Sylvain Joyeux bir.sylvain at gmail.com
Wed Jul 16 10:26:26 CEST 2014


One good news: it appears that we *can* buil the tool out-of-tree ...
Having to get llvm / clang each time is really not a good way forward.
I am fighting against the "right" list of libraries that are needed to
get it right ...

On Wed, Jul 16, 2014 at 9:34 AM, Sylvain Joyeux <bir.sylvain at gmail.com> wrote:
> One question: why do you have to provide the 'build' directory to the tool ?
>
> On Wed, Jul 16, 2014 at 9:33 AM, Sylvain Joyeux <bir.sylvain at gmail.com> wrote:
>>> what i meant: get a list of all types defined in a a given header file--
>>> so that only the types defined in a certain set of headers are seen by
>>> typelib at all. prior to obtaining the actual memory-layout. this would
>>> save us a lot of processing, and keep the tlb-files smaller
>> That's exactly what we need. Typelib currently has to filter it out of
>> the gccxml output (which makes the gccxml output horribly big).
>>
>> Thanks for getting into it, we all agree that getting rid of gccxml is
>> a very very nice to have ...
>>
>> Sylvain


More information about the Rock-dev mailing list