diff options
Diffstat (limited to 'llvm/docs')
| -rw-r--r-- | llvm/docs/CMake.rst | 8 | ||||
| -rw-r--r-- | llvm/docs/FAQ.rst | 6 | ||||
| -rw-r--r-- | llvm/docs/HowToReleaseLLVM.rst | 3 | ||||
| -rw-r--r-- | llvm/docs/ProgrammersManual.rst | 4 |
4 files changed, 7 insertions, 14 deletions
diff --git a/llvm/docs/CMake.rst b/llvm/docs/CMake.rst index 3234eb0d57f..507a85d0952 100644 --- a/llvm/docs/CMake.rst +++ b/llvm/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/llvm/docs/FAQ.rst b/llvm/docs/FAQ.rst index ef8b0c886bf..2c69abfdd0b 100644 --- a/llvm/docs/FAQ.rst +++ b/llvm/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/llvm/docs/HowToReleaseLLVM.rst b/llvm/docs/HowToReleaseLLVM.rst index ec3362e97b6..e85faf7eadf 100644 --- a/llvm/docs/HowToReleaseLLVM.rst +++ b/llvm/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/llvm/docs/ProgrammersManual.rst b/llvm/docs/ProgrammersManual.rst index fe5e6610dc8..b6d751d7cbe 100644 --- a/llvm/docs/ProgrammersManual.rst +++ b/llvm/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: |
