Tanner Gooding

ClangSharp and libClangSharp now provide a `linux-x64` component which should assist in many scenarios "just working". It's worth noting, however, this is a "best attempt" and LLVM/Clang themselves often need...

This resolves the libraries based on the default search paths for the system and so it will preference an exact match before trying to fallback to just `libclang`. The NuGet...

Closing this as the original issue was answered. Newer versions of ClangSharp now validate the loaded version of libClang matches the expected version.

My expectation is the failure is caused by a version mismatch. You are running ClangSharpPInvokeGenerator `v11.0.0-beta3`, but the installed `libClang` is `10.0.0-4ubuntu1`. There is a strict requirement that the major...

> Sorry for all the questions. No worries, not all of this is super clear today. Hopefully the issues can get resolved and the tooling can move to a place...

Hmmm. I just tried on a clean machine and everything looks to work as expected. ### ClangSharp 13.0.0 I did the following * `sudo apt install git gcc clang-13 llvm-13-dev`...

> Would you be ok if I submitted a PR for the README with some of these steps in there? Or do you think this would change too often to...

What would this path be relative to? A separate/explicitly stated option?

Could you clarify what version of libClang is being loaded? I'd guess there is a mismatch between what you have on the box and the version of ClangSharp you are...

There are a few scenarios, especially as you get to more C++ oriented code, that aren't going to be correctly handled today. It's something that I typically fix as the...