diff options
| author | Rafael Espindola <rafael.espindola@gmail.com> | 2013-07-25 20:25:31 +0000 |
|---|---|---|
| committer | Rafael Espindola <rafael.espindola@gmail.com> | 2013-07-25 20:25:31 +0000 |
| commit | 1a9e24844fc8e9f147d0722c7384523e843bd5bb (patch) | |
| tree | d90e8ea0b323339736924ec94e0db7a33d8927d8 /docs/MakefileGuide.rst | |
| parent | cb420a4bc066b0b85e50b0c362ae20519d28788c (diff) | |
| download | llvm-1a9e24844fc8e9f147d0722c7384523e843bd5bb.tar.gz llvm-1a9e24844fc8e9f147d0722c7384523e843bd5bb.tar.bz2 llvm-1a9e24844fc8e9f147d0722c7384523e843bd5bb.tar.xz | |
Remove dead code from the makefile build system.
Back in r140220 we removed the autoconf code that would set LLVMCC_OPTION
since it was only used by the test-suite. This patch now removes code
that would only be used if LLVMCC_OPTION was set.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@187154 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/MakefileGuide.rst')
| -rw-r--r-- | docs/MakefileGuide.rst | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/docs/MakefileGuide.rst b/docs/MakefileGuide.rst index 3e90907886..0bb4a3ccd1 100644 --- a/docs/MakefileGuide.rst +++ b/docs/MakefileGuide.rst @@ -172,26 +172,6 @@ intend to be loaded into an tool via the ``-load`` option. `Pass documentation <writing-an-llvm-pass-makefile>`_ has an example of why you might want to do this. -Bitcode Modules -^^^^^^^^^^^^^^^ - -In some situations, it is desirable to build a single bitcode module from a -variety of sources, instead of an archive, shared library, or bitcode -library. Bitcode modules can be specified in addition to any of the other types -of libraries by defining the `MODULE_NAME`_ variable. For example: - -.. code-block:: makefile - - LIBRARYNAME = mylib - BYTECODE_LIBRARY = 1 - MODULE_NAME = mymod - -will build a module named ``mymod.bc`` from the sources in the directory. This -module will be an aggregation of all the bitcode modules derived from the -sources. The example will also build a bitcode archive containing a bitcode -module for each compiled source file. The difference is subtle, but important -depending on how the module or library is to be linked. - Loadable Modules ^^^^^^^^^^^^^^^^ @@ -486,9 +466,6 @@ system that tell it what to do for the current directory. files. These sources will be built before any other target processing to ensure they are present. -``BYTECODE_LIBRARY`` - If set to any value, causes a bitcode library (.bc) to be built. - ``CONFIG_FILES`` Specifies a set of configuration files to be installed. @@ -590,13 +567,6 @@ system that tell it what to do for the current directory. setting this variable without also setting ``SHARED_LIBRARY`` will have no effect. -.. _MODULE_NAME: - -``MODULE_NAME`` - Specifies the name of a bitcode module to be created. A bitcode module can - be specified in conjunction with other kinds of library builds or by - itself. It constructs from the sources a single linked bitcode file. - ``NO_INSTALL`` Specifies that the build products of the directory should not be installed but should be built even if the ``install`` target is given. This is handy @@ -739,12 +709,6 @@ The override variables are given below: ``LLVMAS`` (defaulted) Specifies the path to the ``llvm-as`` tool. -``LLVMCC`` - Specifies the path to the LLVM capable compiler. - -``LLVMCXX`` - Specifies the path to the LLVM C++ capable compiler. - ``LLVMGCC`` (defaulted) Specifies the path to the LLVM version of the GCC 'C' Compiler. @@ -888,8 +852,6 @@ internal. You should not use these variables under any circumstances. Archive AR.Flags BaseNameSources - BCCompile.C - BCCompile.CXX BCLinkLib C.Flags Compile.C @@ -936,7 +898,6 @@ internal. You should not use these variables under any circumstances. LLVMUsedLibs LocalTargets Module - ObjectsBC ObjectsLO ObjectsO ObjMakefiles |