[aur-general] How to name llvm trunk packages tailored to work with mesa trunk ?
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-git builds for lots of processor architectures not supported by archlinux. RISC-V is one of them. 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
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
On 08-05-2019 14:58, Eli Schwartz via aur-general wrote:
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.
mesa requires llvm and clang (compiler-rt is needed for clang) , minimal may fit that.
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 guess it's for cross compilation purposes. Both extra/llvm and aur llvm-git use llvm default[1] to build all supported architecture targets. The full list of targets is in https://github.com/llvm/llvm-project/blob/master/llvm/CMakeLists.txt and shows 15 targets. I'm not sure, but maybe MIPS is the RISC-V architecture ? LW [1]https://llvm.org/docs/CMake.html#llvm-specific-variables *> LLVM_TARGETS_TO_BUILD*:STRING Semicolon-separated list of targets to build, or /all/ for building all targets. Case-sensitive. Defaults to /all/. Example: |-DLLVM_TARGETS_TO_BUILD="X86;PowerPC"|.
On 08-05-2019 15:19, Lone_Wolf wrote:
On 08-05-2019 14:58, Eli Schwartz via aur-general wrote:
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.
mesa requires llvm and clang (compiler-rt is needed for clang) , minimal may fit that.
I've thought it over and minimal does fit much better then previous attempts. Busy rewriting PKGBUILDs to this new naming scheme. Lone_Wolf
participants (2)
-
Eli Schwartz
-
Lone_Wolf