Hi,
On 28-01-16 09:36, Hans de Goede wrote:
Hi,
On 27-01-16 19:22, Adam Jackson wrote:
On Wed, 2016-01-27 at 11:25 -0500, Neal Gompa wrote:
Aren't clang, lldb, and compiler-rt still part of the main LLVM
package sources, though? It would make sense to continue building them
as part of the LLVM package since they ship together.
They're distributed as separate tarballs, if that's what you mean:
hyoscyamine:~/fedora% grep ^Source0 {compiler-rt,clang,lldb}/*.spec
compiler-rt/compiler-rt.spec:Source0: http://llvm.org/releases/%{version}/%{name}-%{version}.src.tar.xz
clang/clang.spec:Source0: http://llvm.org/releases/%{version}/cfe-%{version}.src.tar.xz
lldb/lldb.spec:Source0: http://llvm.org/releases/%{version}/%{name}-%{version}.src.tar.xz
Right, unfortunately mesa/gallium does not only need llvm-core it also needs clang, quoting
from src/gallium/state_trackers/clover/llvm/invocation.cpp :
#include <clang/Frontend/CompilerInstance.h>
...
llvm::Module *
compile_llvm(llvm::LLVMContext &llvm_ctx, const std::string &source,
const header_map &headers,
const std::string &name, const std::string &triple,
const std::string &processor, const std::string &opts,
clang::LangAS::Map& address_spaces, unsigned &optimization_level
std::string &r_log) {
clang::CompilerInstance c;
...
So if no one from the community steps up as a clang pkg maintainer the graphics team
will still need to maintain it for opencl support in mesa.
Also I'm not sure if clang can be build outside of the llvm directory hierarchy
(this might be possible, but I've never tried), so I'm not sure if clang can
easily be split into a separate package.
Ok, never mind about the splitting up bit, I see that clang already is a separate
pkg (this is not how it is typically build when building directly from git),
I assume that is going to stay the same when moving from autotools to cmake.
Regards,
Hans
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
