On Sun, 2024-12-08 at 04:11 +0000, Sam James wrote: > I'm not sure if I'm sold on *two*. What happens for stuff like mlir > where it's not a runtime but it's arguably more of one than core? > > It just doesn't feel like the division works great. Or maybe it's just > because I feel like llvm-core will keep growing and llvm-runtimes won't.
Well, upstream has a split between "projects" and "runtimes", and I think it makes sense to follow that. "compiler-rt" and "libc" happen to be listed in both, but I suppose it's more of a historical thing -- I think you're always supposed to be doing the runtimes build for projects that support it these days. Right now, we don't package libc, pstl, llvm-libgcc -- so there are definitely more potential packages to be added. I suspect that this split will also help with crossdev. FWIU we only need to cover runtimes there, since the toolchain itself is cross- capable by design. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
