From fe4f8765dcab5e126cf6e2d8592e2e85bc6d59d8 Mon Sep 17 00:00:00 2001 From: Sven van Haastregt Date: Wed, 3 Jul 2019 09:57:59 +0000 Subject: [PATCH] Remove some autoconf references from docs and comments The autoconf build system support has been removed a while ago, remove some outdated references. Differential Revision: https://reviews.llvm.org/D63608 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@365013 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CMake.rst | 8 ++++---- docs/FAQ.rst | 6 ------ docs/HowToReleaseLLVM.rst | 3 +-- docs/ProgrammersManual.rst | 4 ++-- lib/Support/Errno.cpp | 2 +- lib/Support/PrettyStackTrace.cpp | 2 +- lib/Support/Unix/Unix.h | 2 +- 7 files changed, 10 insertions(+), 17 deletions(-) diff --git a/docs/CMake.rst b/docs/CMake.rst index 3234eb0d57fd..507a85d09526 100644 --- a/docs/CMake.rst +++ b/docs/CMake.rst @@ -662,10 +662,10 @@ cross-compiling. Embedding LLVM in your project ============================== -From LLVM 3.5 onwards both the CMake and autoconf/Makefile build systems export -LLVM libraries as importable CMake targets. This means that clients of LLVM can -now reliably use CMake to develop their own LLVM-based projects against an -installed version of LLVM regardless of how it was built. +From LLVM 3.5 onwards the CMake build system exports LLVM libraries as +importable CMake targets. This means that clients of LLVM can now reliably use +CMake to develop their own LLVM-based projects against an installed version of +LLVM regardless of how it was built. Here is a simple example of a CMakeLists.txt file that imports the LLVM libraries and uses them to build a simple application ``simple-tool``. diff --git a/docs/FAQ.rst b/docs/FAQ.rst index ef8b0c886bfa..2c69abfdd0bc 100644 --- a/docs/FAQ.rst +++ b/docs/FAQ.rst @@ -45,12 +45,6 @@ systems. Most of the code is written in standard C++ with operating system services abstracted to a support library. The tools required to build and test LLVM have been ported to a plethora of platforms. -Some porting problems may exist in the following areas: - -* The autoconf/makefile build system relies heavily on UNIX shell tools, - like the Bourne Shell and sed. Porting to systems without these tools - (MacOS 9, Plan 9) will require more effort. - What API do I use to store a value to one of the virtual registers in LLVM IR's SSA representation? --------------------------------------------------------------------------------------------------- diff --git a/docs/HowToReleaseLLVM.rst b/docs/HowToReleaseLLVM.rst index ec3362e97b6f..e85faf7eadf1 100644 --- a/docs/HowToReleaseLLVM.rst +++ b/docs/HowToReleaseLLVM.rst @@ -109,9 +109,8 @@ Update LLVM Version ^^^^^^^^^^^^^^^^^^^ After creating the LLVM release branch, update the release branches' -``autoconf`` and ``configure.ac`` versions from '``X.Ysvn``' to '``X.Y``'. +``CMakeLists.txt`` versions from '``X.Ysvn``' to '``X.Y``'. Update it on mainline as well to be the next version ('``X.Y+1svn``'). -Regenerate the configure scripts for both ``llvm`` and the ``test-suite``. In addition, the version numbers of all the Bugzilla components must be updated for the next release. diff --git a/docs/ProgrammersManual.rst b/docs/ProgrammersManual.rst index fe5e6610dc8d..b6d751d7cbe9 100644 --- a/docs/ProgrammersManual.rst +++ b/docs/ProgrammersManual.rst @@ -3387,8 +3387,8 @@ compatible LLVM libraries built without it defined. By default, turning on assertions also turns on `LLVM_ENABLE_ABI_BREAKING_CHECKS` so a default +Asserts build is not ABI compatible with a default -Asserts build. Clients that want ABI compatibility -between +Asserts and -Asserts builds should use the CMake or autoconf -build systems to set `LLVM_ENABLE_ABI_BREAKING_CHECKS` independently +between +Asserts and -Asserts builds should use the CMake build system +to set `LLVM_ENABLE_ABI_BREAKING_CHECKS` independently of `LLVM_ENABLE_ASSERTIONS`. .. _coreclasses: diff --git a/lib/Support/Errno.cpp b/lib/Support/Errno.cpp index 485378dfdc98..d18231c6ebf5 100644 --- a/lib/Support/Errno.cpp +++ b/lib/Support/Errno.cpp @@ -11,7 +11,7 @@ //===----------------------------------------------------------------------===// #include "llvm/Support/Errno.h" -#include "llvm/Config/config.h" // Get autoconf configuration settings +#include "llvm/Config/config.h" #include "llvm/Support/raw_ostream.h" #include diff --git a/lib/Support/PrettyStackTrace.cpp b/lib/Support/PrettyStackTrace.cpp index 8863dea67ddc..497084ecda95 100644 --- a/lib/Support/PrettyStackTrace.cpp +++ b/lib/Support/PrettyStackTrace.cpp @@ -14,7 +14,7 @@ #include "llvm/Support/PrettyStackTrace.h" #include "llvm-c/ErrorHandling.h" #include "llvm/ADT/SmallString.h" -#include "llvm/Config/config.h" // Get autoconf configuration settings +#include "llvm/Config/config.h" #include "llvm/Support/Compiler.h" #include "llvm/Support/Signals.h" #include "llvm/Support/Watchdog.h" diff --git a/lib/Support/Unix/Unix.h b/lib/Support/Unix/Unix.h index 20d70bd2fcee..86309b0567f5 100644 --- a/lib/Support/Unix/Unix.h +++ b/lib/Support/Unix/Unix.h @@ -18,7 +18,7 @@ //=== is guaranteed to work on all UNIX variants. //===----------------------------------------------------------------------===// -#include "llvm/Config/config.h" // Get autoconf configuration settings +#include "llvm/Config/config.h" #include "llvm/Support/Chrono.h" #include "llvm/Support/Errno.h" #include