While using LLVMSharp 5.0.0 from Nuget on Windows, I noticed a minor issue where none of the InitializeAll and InitializeNative entry points can be found in libLLVM. I say minor as the Initialize functions for specific targets works fine as a workaround.
After a export dump of libLLVM.dll I found InitializeAll and InitializeNative functions have leading underscores which don't match the specified EntryPoints in the bindings.
As these function names seem to be inconsistent with all other exported functions this looks like an issue for LLVM-C rather than a LLVMSharp, but as I found it using LLVMSharp I'll raise it here first incase the solution is to just update the bindings. I haven't confirmed if other bindings have a similar issue.
While using LLVMSharp 5.0.0 from Nuget on Windows, I noticed a minor issue where none of the InitializeAll and InitializeNative entry points can be found in libLLVM. I say minor as the Initialize functions for specific targets works fine as a workaround.
After a export dump of libLLVM.dll I found InitializeAll and InitializeNative functions have leading underscores which don't match the specified EntryPoints in the bindings.
As these function names seem to be inconsistent with all other exported functions this looks like an issue for LLVM-C rather than a LLVMSharp, but as I found it using LLVMSharp I'll raise it here first incase the solution is to just update the bindings. I haven't confirmed if other bindings have a similar issue.
X86 Initialize Functions (for reference)
InitializeAll Functions
InitializeNative Functions