Does anyone reading this have experience submitting bugs to the LLVM project? If I submit to the llvm-project github issues page is that a place that actually gets looked at?
Yes, this is still about fucking libunwind. I think I'm going to wind up filing five separate bugs on four separate projects by the time I'm done with this. And this may or may not actually get me any closer to actually being able to build programs with libc++
Okay, actually, here is a question. Has anyone reading this ever used the program `llvm-config`? Is llvm-config meant to be used with *clang*, or is it meant to be used when linking raw llvm with like idk IR or something? That is, is llvm-config a replacement for pkg-config used by llvm projects, or is it a different thing entirely?
@mcc “how do I link libllvm, which is actually 40 different libs, into my dotnet runtime? I use the flags llvm-config —libs tells me”
@directhex okay. but do you do this with clang, with lld, with llc, directly against the llvm libraries with some C# tooling?
@directhex sorry i mean like, what program do you pass those flags to?

@mcc @directhex it's for programs that want to use the LLVM C++ API or libclang, so basically custom tooling for C or programming language implementations.

I've used llvm-config via llvm-sys to obtain a C AST for a C-to-Rust transpiler, and make it link my patched libclang fork.

It's just a take on pkg-config, avoiding pkg-config's limitations and inconsistent support. libpng-config exists for the same reasons.

https://gitlab.com/taricorp/llvm-sys.rs/-/blob/main/build.rs?ref_type=heads

build.rs · main · Peter Marheine / llvm-sys.rs · GitLab

Rust bindings to LLVM's C API.

GitLab