>
> 1) I would like to compile LLVM with cmake as I'm used to... which flags I
> shoud use ?
see `deps/llvm-svn/build_Release/config.log` for the flags we pass in, and
try to mirror at least some of those.
2) Maybe there is some trick : llvm-config --cxxflags can give flags
> different from the llvm compilation flags
I don't follow...
3) Is there, in general, a one-to-one correspondance between cmake flags
> and configure flags ? and particularly for llvm ?
It depends on the flags. CMake does a lot of platform detection so some
flags may not be necessary.
3) at the end, can we adapt the build of Cxx.jl for an external LLVM ?
> because Pkg.clone("...") and the Pkg.build("...") require the internal llvm.
Provided you have also built LLDB and Clang with compatible flags, I don't
see any reason why not. I believe the Cxx.jl build script just uses
llvm-config, but you might need to teach it where to find some things, if
it makes any hard-coded assumptions.
4) bonus question : is it avoidable , the fact that sagemath comes with his
> own python, youcompleteme (vim plugin) comes with it's own llvm/clang,
> cling (cern interpreter) comes with it's own llvm/clang
No idea about Sage/Python, but with respect to Linux and LLVM, part of the
issue is that some distributions are militant about bumping LLVM versions
without realizing how much the LLVM API changes from version to version.
(another issue is that getting patches in to LLVM can sometimes be
slow/difficult, so groups like Cling maintain their own fork, as we
unfortunately may have to do)
Relatedly, see: https://github.com/JuliaLang/julia/pull/9422 (although IIRC
it is not driving the LLVM CMake build directly yet)
