Comment 19 for bug 991493

Revision history for this message
Mike Henry (mike-henry) wrote :

Using update-alternatives goes for all the other LLVM-tools as well, even though using llvm-config makes it a little easier to use.

This is the state of my LLVM tools in /usr/bin after installing 3.5. Had I been able to select whether to use 3.5 or 3.4 and had all links updated, then things would have been a lot easier..

/usr/bin$ ls llvm-*
llvm-ar-3.4 llvm-config-3.5 llvm-extract-3.4 llvm-nm-3.5 llvm-rtdyld-3.5
llvm-ar-3.5 llvm-cov-3.4 llvm-extract-3.5 llvm-objdump-3.4 llvm-size-3.4
llvm-as-3.4 llvm-cov-3.5 llvm-link-3.4 llvm-objdump-3.5 llvm-size-3.5
llvm-as-3.5 llvm-diff-3.4 llvm-link-3.5 llvm-prof-3.4 llvm-stress-3.4
llvm-bcanalyzer-3.4 llvm-diff-3.5 llvm-mc-3.4 llvm-ranlib-3.4 llvm-stress-3.5
llvm-bcanalyzer-3.5 llvm-dis-3.4 llvm-mc-3.5 llvm-ranlib-3.5 llvm-symbolizer-3.4
llvm-clang llvm-dis-3.5 llvm-mcmarkup-3.4 llvm-readobj-3.4 llvm-symbolizer-3.5
llvm-config llvm-dwarfdump-3.4 llvm-mcmarkup-3.5 llvm-readobj-3.5 llvm-tblgen-3.4
llvm-config-3.4 llvm-dwarfdump-3.5 llvm-nm-3.4 llvm-rtdyld-3.4 llvm-tblgen-3.5

(llvm-clang points to clang, which is not versioned. I created llvm-config myself using update-alternatives.)

I believe a llvm_select package is even available in MacPorts, which is a really nice feature to have: "port select --set llvm llvm-3.4". Makes it really easy to switch between LLVM versions.