Make ClangSharpPInvokeGenerator --version output native library versions about clangsharp HOT 3 CLOSED

Ah, I see. That should be trivial enough to add given that its validating things on the normal path now.

from clangsharp.

@FiniteReality, the tooling now runs explicit logic to validate the loaded library version is as expected (https://github.com/microsoft/ClangSharp/blob/main/sources/ClangSharp.PInvokeGenerator/PInvokeGenerator.cs#L58-L70):

            var clangVersion = clang.getClangVersion().ToString();

            if (!clangVersion.Contains("13.0.0"))
            {
                throw new InvalidOperationException($"Invalid libClang version. Returned string '{clangVersion}' does not contain '{ExpectedClangVersion}'");
            }

            var clangSharpVersion = clangsharp.getVersion().ToString();

            if (!clangSharpVersion.Contains("13.0.0"))
            {
                throw new InvalidOperationException($"Invalid libClang version. Returned string '{clangSharpVersion}' does not contain '{ExpectedClangSharpVersion}'");
            }

Outside of this, there isn't much that can be done as DllNotFoundException is handled internally by the runtime interop handling; so this is a matter of it not finding libClangSharp in the first place. Setting LD_DEBUG would be the right way to determine what paths where being searched for libClangSharp in this scenario (as .NET and ClangSharp simply use the system default).

from clangsharp.

Yeah. The idea was that I could use ClangSharpPInvokeGenerator --version to check that it can find and load the libraries without having it try to do any actual work.

from clangsharp.