[LLVMdev] RFC: Timeline for deprecating the autoconf build system?

Wed Dec 3 01:08:46 PST 2014

> - Is there any technical reason why the remaining autoconf users can't switch
>   to CMake?

I can't see how to do 'configure --disable-assertions --disable-optimized', using CMake in LLVM. This is useful for example to build for coverage testing.

(Also, it seems like CMake still don't take the CPPFLAGS environment variable (for example, for passing a custom -I path) : http://www.cmake.org/Bug/view.php?id=12928. It is inconvenient to set both CFLAGS and CXXFLAGS for this.)

/Patrik Hägglund

-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Tom Stellard
Sent: den 31 oktober 2014 23:08
To: llvmdev at cs.uiuc.edu
Subject: [LLVMdev] RFC: Timeline for deprecating the autoconf build system?

Hi,

I would like to propose deprecating the autoconf build system at some
point in the future.  Maintaining two build systems is a hassle not
only for this project, but also for other projects that use LLVM
and have to deal with the slight differences in output between the two
build systems.

It seems like most people are using CMake at this point, so my questions
to the community are:

- Is there any technical reason why the remaining autoconf users can't switch
  to CMake?

For example, I personally use automake, and the only reason I don't
use CMake is because it doesn't produce a single shared object
(e.g. libLLVM-3.6.0svn.so).

- What is a reasonable timeframe to allow the remaining autoconf users
  a chance to migrate to CMake?

Thanks,
Tom
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev