Tanner Gooding
Tanner Gooding
This is provided now: https://www.nuget.org/packages/libClangSharp.runtime.osx-arm64
I've got a fix up for the first issue here: https://github.com/dotnet/ClangSharp/pull/390. I forgot to also trim the `union Name` case for C. It's not an issue when targeting C++. I...
This likely means that an unsupported type declaration was also encountered and the size/alignment for it was not changed from the default. The else block that adds the diagnostic should...
This one isn't repro'ing anymore. I believe I fixed it a while back when I adjusted the handling to use `-1` as the default.
It looks like the clang installed with `xcode` isn't part of the default resolution paths for arbitrary tools. You'd need to ensure it is resolvable either by adding the relevant...
> I wonder if the default search paths need revision for MacOS platform? .NET simply uses the system default resolution path for a given platform. If .NET can't resolve it...
You need both `libClangSharp` and `libclang` to be resolvable. Its reporting to fail to find the latter.
It might be and there is no corresponding version of `libClangSharp` for Apple M1 today. I'd expect if you ran it under x64 mode it would work however. Notably, the...
I'm publishing osx-arm64 binaries as part of v15.0.0 (going to track via https://github.com/dotnet/ClangSharp/issues/345).
@miloush could you provide more context on this. It looks like you've got an invalid declaration in the first place as `GUID { }` is going to expect a initializer...