Albert Graef <Dr.Graef at t-online.de> writes:> On 06/21/2012 04:22 PM, Óscar Fuentes wrote: >> About the "many features" that cmake lacks, can you provide a list, >> please? > > Generally it works fairly well, but here are some differences to the > autoconf-based build I noticed: > > - No 'make uninstall'. That is a real deal breaker if you want to > quickly try a new LLVM version. I know that cmake doesn't provide this > out of the box, but then it should be added as a custom target.You can work with LLVM without installing, or install it on a specific directory that you can delete afterwards. That's much better than overwriting/removing the previous version.> - No libLLVM-<version>.so. I get this with the autoconf-based build if > shared libraries are enabled, but not with the cmake build.This is very easy to implement.> - libclang ends up as liblibclang.so (building clang along with LLVM). > Surely that's not intended?There was some discussion about this on the past, but I can't recall all the details. In any case, it is something easy enough to change.
On 22 Jun 2012, at 00:08, Óscar Fuentes wrote:> Albert Graef <Dr.Graef at t-online.de> writes: > - libclang ends up as liblibclang.so (building clang along with LLVM). >> Surely that's not intended? > > There was some discussion about this on the past, but I can't recall all > the details. In any case, it is something easy enough to change.This should be fixed as of 3.1. See http://llvm.org/bugs/show_bug.cgi?id=12620 for the fix, and links to previous discussions.
On 06/22/2012 01:08 AM, Óscar Fuentes wrote:> You can work with LLVM without installing, or install it on a specific > directory that you can delete afterwards. That's much better than > overwriting/removing the previous version.No, in general it's not. It's fairly common to install LLVM under a standard prefix such as /usr or /usr/local so that its headers and libraries are found by LLVM applications without any ado. In any case, cmake does install into /usr/local by default on Un*x-like systems, so a corresponding 'make uninstall' target should be offered as well. Support for 'make uninstall' is pretty standard these days. I consider that an important feature, and I'm surely not alone with this. Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr.Graef at t-online.de, ag at muwiinfa.geschichte.uni-mainz.de WWW: http://www.musikinformatik.uni-mainz.de/ag
On 06/22/2012 12:10 PM, Albert Graef wrote:> In any case, cmake does install into /usr/local by default on Un*x-like > systems, so a corresponding 'make uninstall' target should be offered as > well. Support for 'make uninstall' is pretty standard these days. I > consider that an important feature, and I'm surely not alone with this.Just for the record, there's also an entry in the cmake FAQ about this: http://www.cmake.org/Wiki/CMake_FAQ#Can_I_do_.22make_uninstall.22_with_CMake.3F -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr.Graef at t-online.de, ag at muwiinfa.geschichte.uni-mainz.de WWW: http://www.musikinformatik.uni-mainz.de/ag
On 06/22/2012 07:42 AM, David Röthlisberger wrote:> On 22 Jun 2012, at 00:08, Óscar Fuentes wrote: >> > Albert Graef <Dr.Graef at t-online.de> writes: >> > - libclang ends up as liblibclang.so (building clang along with LLVM). >>> >> Surely that's not intended? >> > >> > There was some discussion about this on the past, but I can't recall all >> > the details. In any case, it is something easy enough to change. > > This should be fixed as of 3.1. See > http://llvm.org/bugs/show_bug.cgi?id=12620 for the fix, and links > to previous discussions.I tried this with the official 3.1 tarballs of LLVM and clang from the Download page, and liblibclang.so is what I got using the cmake build on Linux. So no, to me it doesn't seem to be fixed in 3.1. The linked thread on clang-dev seems inconclusive to me as well. Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr.Graef at t-online.de, ag at muwiinfa.geschichte.uni-mainz.de WWW: http://www.musikinformatik.uni-mainz.de/ag