X-Git-Url: http://plrg.eecs.uci.edu/git/?p=oota-llvm.git;a=blobdiff_plain;f=docs%2FMakefileGuide.html;h=5f561f3a9783cb7de9efde15cf7a5ea814e1fc21;hp=c13e06fb1f08217620c37273ff143dbc618156e2;hb=a15dc035a6d4153bece7a067e037e5d6f5d58b16;hpb=434262ad518dad47841189b27fb9f3943d8206b8 diff --git a/docs/MakefileGuide.html b/docs/MakefileGuide.html index c13e06fb1f0..5f561f3a978 100644 --- a/docs/MakefileGuide.html +++ b/docs/MakefileGuide.html @@ -30,7 +30,7 @@
  1. Libraries
      -
    1. Bytecode Modules
      2. +
    2. Bitcode Modules
    3. Loadable Modules
    2. @@ -260,11 +260,11 @@ -
    Bytecode Modules
    +
    Bitcode Modules
    -

    In some situations, it is desireable to build a single bytecode module from - a variety of sources, instead of an archive, shared library, or bytecode - library. Bytecode modules can be specified in addition to any of the other +

    In some situations, it is desireable 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:

    
@@ -273,9 +273,9 @@
       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 bytecode modules - derived from the sources. The example will also build a bytecode archive - containing a bytecode module for each compiled source file. The difference is + 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.

    @@ -626,7 +626,7 @@ 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 bytecode library (.bc) to be built.
    +
    If set to any value, causes a bitcode library (.bc) to be built.
    CONFIG_FILES
    Specifies a set of configuration files to be installed.
    DIRS
    @@ -709,9 +709,9 @@ setting this variable without also setting SHARED_LIBRARY will have no effect.
    MODULE_NAME
    -
    Specifies the name of a bytecode module to be created. A bytecode +
    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 bytecode + 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 @@ -781,8 +781,6 @@
    AR (defaulted)
    Specifies the path to the ar tool.
    -
    BISON(configured)
    -
    Specifies the path to the bison tool.
    PROJ_OBJ_DIR
    The directory into which the products of build rules will be placed. This might be the same as @@ -808,17 +806,10 @@ isn't one.
    ECHO(configured)
    Specifies the path to the echo tool for printing output.
    -
    ETAGS(configured)
    -
    Specifies the path to the etags tool.
    -
    ETAGSFLAGS(configured) -
    -
    Provides flags to be passed to the etags tool.
    EXEEXT(configured)
    Provides the extension to be used on executables built by the makefiles. The value may be empty on platforms that do not use file extensions for executables (e.g. Unix).
    -
    FLEX(configured)
    -
    Specifies the path to the flex tool.
    INSTALL(configured)
    Specifies the path to the install tool.
    LDFLAGS(configured)
    @@ -835,7 +826,7 @@
    LLVMGXX(defaulted)
    Specifies the path to the LLVM version of the GCC C++ Compiler
    LLVMLD(defaulted)
    -
    Specifies the path to the LLVM bytecode linker tool
    +
    Specifies the path to the LLVM bitcode linker tool
    LLVM_OBJ_ROOT(configured)
    Specifies the top directory into which the output of the build is @@ -884,8 +875,8 @@
    BuildMode
    The name of the type of build being performed: Debug, Release, or Profile
    -
    bytecode_libdir
    -
    The directory into which bytecode libraries will ultimately be +
    bytecode_libdir
    +
    The directory into which bitcode libraries will ultimately be installed. This value is derived from the --prefix option given to configure.
    ConfigureScriptFLAGS
    @@ -965,7 +956,7 @@ CXX.Flags DependFiles DestArchiveLib - DestBytecodeLib + DestBitcodeLib DestModule DestRelinkedLib DestSharedLib @@ -986,8 +977,6 @@ INCFiles InternalTargets LD.Flags - LexFiles - LexOutput LibName.A LibName.BC LibName.LA @@ -1001,9 +990,6 @@ LLVMToolDir LLVMUsedLibs LocalTargets - LTCompile.C - LTCompile.CXX - LTInstall Module ObjectsBC ObjectsLO @@ -1025,8 +1011,6 @@ ToolBuildPath TopLevelTargets UserTargets - YaccFiles - YaccOutput

    @@ -1034,9 +1018,9 @@
    Valid CSS! + src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"> Valid HTML 4.01! + src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"> Reid Spencer
    The LLVM Compiler Infrastructure