[LLVMdev] Deprecating autoconf/make?

Tom Stellard tom at stellard.net
Wed May 22 19:41:38 PDT 2013

On Wed, May 22, 2013 at 04:14:06PM -0700, Eric Christopher wrote:
> Hi All,
> I fear starting another centi-thread on this but I'll give it a shot.
> We're currently supporting two build systems which is definitely one
> more than we (or I) want to support.
> I don't know of any support in autoconf past the
> --host/--build/--target case that's not supported in cmake. I'll send
> out an assertion here that this support isn't necessary and any system
> that needs it can instead move to:
> build native clang
> build next clang with some target that supplies a sysroot and a
> -target option to the native clang
> Can anyone see good a reason not to move to cmake as our only build
> configuration system and drop future support for autoconf + makefiles
> now that 3.3 has branched?

I'm not sure if this is still the case, but at one point autoconf and
CMake were generating shared objects differently.  autoconf builds placed
everything in one shared object, while cmake builds placed each component in
its own shared library.

I don't think this is something that would prevent LLVM from switching
to CMake, but it is one potential trouble spot for users.


More information about the llvm-dev mailing list