[llvm-dev] [RFC] Removing autoconf from trunk

[Chris Bieneman via llvm-dev]

One last reminder to everyone. Today is the day.

I’m going to start removing autoconf around 1:30.

The patches are:
LLVM: http://reviews.llvm.org/D16471 <http://reviews.llvm.org/D16471>
Clang: http://reviews.llvm.org/D16472 <http://reviews.llvm.org/D16472>
Compiler-RT: http://reviews.llvm.org/D16473 <http://reviews.llvm.org/D16473>
Clang-tools-extra: http://reviews.llvm.org/D16475 <http://reviews.llvm.org/D16475>

Once the LLVM patch lands the autoconf builds everywhere will cease to function.

One last big thank you to everyone in the community that made this happen! By the end of the day today we’ll only be supporting one build system!

-Chris

> On Jan 12, 2016, at 9:35 AM, Chris Bieneman via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> 
> Now that 3.8 is imminently branching with the newly deprecated autoconf I think it is time to propose a process and timeline for removing autoconf support from trunk.
> 
> At this point I believe there should be no users of autoconf for Clang and LLVM that are not supported by CMake, so I would like to propose dropping autoconf support from the cfe and llvm repositories on January 26th (two weeks from today). I believe this gives sufficient time for users to migrate any remaining systems off autoconf. If this timeline doesn’t work for you, please speak up.
> 
> There are still some problematic use cases for building the compiler-rt builtins. Specifically bootstrapping cross-compilers is fragile and in some cases entirely unworkable in CMake. To this end I’m not proposing a full removal of the compiler-rt makefiles at this time. What I would like to propose is that on February 2nd we remove autoconf support for all sanitizer runtimes from compiler-rt.
> 
> We will not be removing the makefile build system from the test-suite project. The CMake build system there is very new, and still nowhere near feature complete.
> 
> For other projects (libcxx, libcxxabi, libunwind…) I’ve not made significant contributions to these projects, so I’d like to defer to more active contributors on those projects, but I am unaware of any blocking issues.
> 
> Questions, comments, concerns, panic, fire, brimstone?
> 
> -Chris
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160126/9b5a65d8/attachment.html>