On 5/8/19 8:41 AM, Lone_Wolf wrote: > Hi, > > > llvm-git (and it's predecessor llvm-svn) is intended to provide a full > implementation of the llvm/clang compiler suite. It's a huge package > that takes a lot of time and processor capacity to build. > > While mesa needs llvm, it only needs a subset. > > examples : > > llvm-git builds with ocaml support, but mesa doesn't use ocaml at all.
llvm-minimal-git, perhaps? If it is just building the core. > llvm-git builds for lots of processor architectures not supported by > archlinux. RISC-V is one of them. Why does llvm-git build for RISC-V at all? Who is using it? > I've been looking into this and tried 2 (bad) naming schemes already. > > The current scheme goes like this : > > lone_wolf-llvm-git , lone_wolf-compiler-rt-git, lone_wolf-clang-git and > lone_wolf-lib32-llvm-git > > > llvm-mesa-git seems to vague, while llvm-trunk-for-mesa-trunk-git feels > clumsy and long. > > Please help me to find a good name for these packages. > > Lone_Wolf -- Eli Schwartz Bug Wrangler and Trusted User
signature.asc
Description: OpenPGP digital signature
