[Rock-dev] clang vs. typelib

[Martin Zenzes]

On 07/16/2014 08:37 PM, Sylvain Joyeux wrote:
> Just tried it out ... clang generates piles of errors because it is
> trying to include GCC headers. Did you encounter anything like it ?
rhetorical standard question: which os? which llvm-branch?
did u "make all" in the llvm-build dir, or just "make extractor"?

I got this kind of error "often" when using clang-based tooling. there 
is the "-isystem" option, which is able to fix this (for example this 
[1]). but this this feels kinda hacky ;-) for me the "release_34" branch 
builds, links and runs just fine on Debian testing
>
> One thing you may have missed: types need to be resolved recursively.
> That is, you need to resolve the fields types, and the fields types of
> the fields types and so on and so forth.
we talked about this, and said that these types are pulled later from 
the typelib-registry? no need to resolve them recursively at the level 
of the clang-based-tool? (which still needs a proper name...)
>
> Other than that, it really looks promising ...
I'm suprised how fast we got to this stage... What would be the next steps?
- definitely speedup
- figuring out how to link against a pre-packaged clang installed in the 
system
- test with clang-3.0

[1] https://github.com/Valloric/YouCompleteMe/issues/303