Tanner Gooding

Closing this as the original issue was addressed. Newer versions of ClangSharp now validate the native library version loaded matches the expected version.

I'm going to recheck this once https://github.com/microsoft/ClangSharp/pull/235 is merged. I'm hoping that this was resolved with Clang 12, but if not I'll look at potential workarounds.

@sotteson1, I have a fix for this here: https://github.com/microsoft/ClangSharp/pull/258

This is being reopened by https://github.com/microsoft/ClangSharp/pull/263. The fix ended up regressing a number of key scenarios and so I've started looking into an alternative fix, but said fix will require...

Upon further investigation, it looks like Clang doesn't expose the necessary metadata in any fashion I can discern. The only way I can determine to correctly detect packing here is...

Closing this. As indicated above, Clang doesn't and cannot surface the relevant metadata. Much of the time the `#pragma pack` directives are under an `#ifdef` in which case they cannot...

Could you please try specifying an output file and not simply a directory? The generator looks to be in single file mode, in which case I believe `-o` is required...

You'd likely need to use ` LD_DEBUG` or `ldd` to determine which dependency is missing. My guess is that its not resolving `libclang-cpp` and that's causing the failure. Since LLVM...

This was an issue with not being able to resolve `libclang-cpp` > @rpath/libclang-cpp.dylib (compatibility version 0.0.0, current version 0.0.0) v14.0.0, which was pushed last weekend, made sure to not depend...

I'll see about doing it this weekend. Its going to require rebuilding `LLVM/Clang v13.0.0` for all supported platforms and then rebuilding/packing `libClangSharp`, so its going to take some time to...