Anton Korobeynikov <anton at korobeynikov.info> writes:> I think cmake system lacks many features of autoconf system. In > addition to already said thing, I think the major missing thing is > cross-compilation support. > You can easy cross-compile llvm/clang via standard > --build/--host/--target flags. If you will show that this will be > possible by cmake - then everything will be fine :)Anton, I've posted this information several times on this list, IIRC some of them after you claimed that cmake can't cross-compile, so I hope this is cleared once and for all: http://llvm.org/docs/CMake.html#cross About the "many features" that cmake lacks, can you provide a list, please? (supposing those features actually are useful for LLVM developers. I know that the configure+make build does things missing on the cmake build, but the later does things missing on the former too.) I asked for that list of missing features multiple times on this list, and nobody ever came with anything.
Oscar,> Anton, I've posted this information several times on this list, IIRC > some of them after you claimed that cmake can't cross-compile, so I hope > this is cleared once and for all: > http://llvm.org/docs/CMake.html#crosscmake certainly can crosscompile. But will you please provide the exact list of options / flags which is necessary to cross-compile llvm/clang from, say, linux/darwin to mingw32? Note that tablege and some support libs need to be configured / built for both build and host systems, so, this certainly won't work out of the box :) -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
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. - No libLLVM-<version>.so. I get this with the autoconf-based build if shared libraries are enabled, but not with the cmake build. - libclang ends up as liblibclang.so (building clang along with LLVM). Surely that's not intended? 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
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.
Nothing on the CMake.html doc discusses incorporating Libc++ into building Clang/LLVM with Libc++. Reading up on putting the trunk of libc++ under /llvm/projects where then Clang has CmakeList.txt files to map to that path looking for libc++ still doesn't compile, even if I first build Clang with GCC and then again with the newly built clang under /usr/local/bin on Debian. It still craps out and throws up several errors regarding C++11 issues. - Marc On 06/21/2012 07:22 AM, Óscar Fuentes wrote:> Anton Korobeynikov<anton at korobeynikov.info> writes: > >> I think cmake system lacks many features of autoconf system. In >> addition to already said thing, I think the major missing thing is >> cross-compilation support. >> You can easy cross-compile llvm/clang via standard >> --build/--host/--target flags. If you will show that this will be >> possible by cmake - then everything will be fine :) > Anton, I've posted this information several times on this list, IIRC > some of them after you claimed that cmake can't cross-compile, so I hope > this is cleared once and for all: > > http://llvm.org/docs/CMake.html#cross > > About the "many features" that cmake lacks, can you provide a list, > please? (supposing those features actually are useful for LLVM > developers. I know that the configure+make build does things missing on > the cmake build, but the later does things missing on the former too.) I > asked for that list of missing features multiple times on this list, and > nobody ever came with anything. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-- Marc J. Driftmeyer Email :: mjd at reanimality.com <mailto:mjd at reanimality.com> Web :: http://www.reanimality.com Cell :: (509) 435-5212 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120621/c85fa3f8/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: mjd.vcf Type: text/x-vcard Size: 317 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120621/c85fa3f8/attachment.vcf>