[llvm] r258873 - Fixing the documentation builds

[Chris Bieneman via llvm-commits]

Author: cbieneman
Date: Tue Jan 26 16:53:12 2016
New Revision: 258873

URL: http://llvm.org/viewvc/llvm-project?rev=258873&view=rev
Log:
Fixing the documentation builds

I broke the documentation builds when I deleted the MakefileGuide as part of the autoconf removal. At some point I'll need to do a more in-depth pass updating the documentation to remove references to the old build system.

Modified:
    llvm/trunk/docs/BuildingLLVMWithAutotools.rst
    llvm/trunk/docs/LLVMBuild.rst
    llvm/trunk/docs/TestingGuide.rst
    llvm/trunk/docs/index.rst

Modified: llvm/trunk/docs/BuildingLLVMWithAutotools.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/BuildingLLVMWithAutotools.rst?rev=258873&r1=258872&r2=258873&view=diff
==============================================================================
--- llvm/trunk/docs/BuildingLLVMWithAutotools.rst (original)
+++ llvm/trunk/docs/BuildingLLVMWithAutotools.rst Tue Jan 26 16:53:12 2016
@@ -203,7 +203,7 @@ source code:
   If you need to update your bitcode libraries, this is the target to use once
   you've built them.
 
-Please see the `Makefile Guide <MakefileGuide.html>`_ for further details on
+Please see the `CMake <CMake.html>`_ documentation for further details on
 these ``make`` targets and descriptions of other targets available.
 
 It is also possible to override default values from ``configure`` by declaring

Modified: llvm/trunk/docs/LLVMBuild.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/LLVMBuild.rst?rev=258873&r1=258872&r2=258873&view=diff
==============================================================================
--- llvm/trunk/docs/LLVMBuild.rst (original)
+++ llvm/trunk/docs/LLVMBuild.rst Tue Jan 26 16:53:12 2016
@@ -49,8 +49,7 @@ Build Integration
 
 The LLVMBuild files themselves are just a declarative way to describe
 the project structure. The actual building of the LLVM project is
-handled by another build system (currently we support both
-:doc:`Makefiles <MakefileGuide>` and :doc:`CMake <CMake>`).
+handled by another build system (See: :doc:`CMake <CMake>`).
 
 The build system implementation will load the relevant contents of the
 LLVMBuild files and use that to drive the actual project build.

Modified: llvm/trunk/docs/TestingGuide.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/TestingGuide.rst?rev=258873&r1=258872&r2=258873&view=diff
==============================================================================
--- llvm/trunk/docs/TestingGuide.rst (original)
+++ llvm/trunk/docs/TestingGuide.rst Tue Jan 26 16:53:12 2016
@@ -99,19 +99,11 @@ is in the ``test-suite`` module. See :re
 Regression tests
 ----------------
 
-To run all of the LLVM regression tests, use the master Makefile in the
-``llvm/test`` directory. LLVM Makefiles require GNU Make (read the :doc:`LLVM
-Makefile Guide <MakefileGuide>` for more details):
+To run all of the LLVM regression tests use the check-llvm target:
 
 .. code-block:: bash
 
-    % make -C llvm/test
-
-or:
-
-.. code-block:: bash
-
-    % make check
+    % make check-llvm
 
 If you have `Clang <http://clang.llvm.org/>`_ checked out and built, you
 can run the LLVM and Clang tests simultaneously using:

Modified: llvm/trunk/docs/index.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/index.rst?rev=258873&r1=258872&r2=258873&view=diff
==============================================================================
--- llvm/trunk/docs/index.rst (original)
+++ llvm/trunk/docs/index.rst Tue Jan 26 16:53:12 2016
@@ -384,7 +384,6 @@ Information about LLVM's development pro
    :hidden:
 
    DeveloperPolicy
-   MakefileGuide
    Projects
    LLVMBuild
    HowToReleaseLLVM
@@ -405,9 +404,6 @@ Information about LLVM's development pro
   Describes the LLVMBuild organization and files used by LLVM to specify
   component descriptions.
 
-:doc:`MakefileGuide`
-  Describes how the LLVM makefiles work and how to use them.
-
 :doc:`HowToReleaseLLVM`
   This is a guide to preparing LLVM releases. Most developers can ignore it.