Provide access to libclang headers needed for accurate parsing about libclang

[chetant]

How are these include files used? I see that we export a function that provides the path, do you add that path in withParse?

[sethfowler]

Nah, I didn't want to force users to always include them. It would be a good idea to provide a higher level function with some nice defaults and some clarification on how to use the path, though. (Essentially you just want to add to the command line arguments a "-I" argument which uses that path.)

[sethfowler]

So it turns out that in the release version of LLVM 3.4, they've fixed this problem. libclang now automatically looks for its headers in the directory containing the library. Once the next GHC is out and we can use dynamic linking, this will be perfect.

For now, I've patched libclang to add clang_setClangResourcesPath which allows us to specify the location of the headers. The nice thing is that because this is a special call instead of being part of the command line arguments passed to clang_parseTranslationUnit and the like, we can totally hide this from the user. I no longer export libclangIncludePath in the updated version of the code.