From: Eli Bendersky Date: Mon, 16 Apr 2012 08:42:55 +0000 (+0000) Subject: Documentation fixes to LLVMBuild.html [PR 11563] X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=4d66f4cc6ec5c5891cf2f626550f503d4b916351;p=oota-llvm.git Documentation fixes to LLVMBuild.html [PR 11563] git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@154804 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/LLVMBuild.html b/docs/LLVMBuild.html index cce607d611f..f39a8a6a1c0 100644 --- a/docs/LLVMBuild.html +++ b/docs/LLVMBuild.html @@ -101,7 +101,7 @@ $ROOT of project trees for things which can be checked out separately. -->

As mentioned earlier, LLVM projects are organized into - logical components. Every component is typically grouped into it's + logical components. Every component is typically grouped into its own subdirectory. Generally, a component is organized around a coherent group of sources which have some kind of clear API separation from other parts of the code.

@@ -190,7 +190,7 @@ required_libraries = Archive BitReader Core Support TransformUtils number in order for files with multiple components ("component_0", "component_1", and so on).

-

Section names not matches this format (or the "common" section) are +

Section names not matching this format (or the "common" section) are currently unused and are disallowed.

Every component is defined by the properties in the section. The exact list @@ -212,7 +212,7 @@ required_libraries = Archive BitReader Core Support TransformUtils

  • parent [required]

    The name of the logical parent of the component. Components are organized into a logical tree to make it easier to navigate and organize - groups of components. The parent's have no semantics as far as the project + groups of components. The parents have no semantics as far as the project build is concerned, however. Typically, the parent will be the main component of the parent directory.

    @@ -263,7 +263,7 @@ required_libraries = Archive BitReader Core Support TransformUtils

    If given, a list of the names of Library or LibraryGroup components which must also be linked in whenever this library is used. That is, the link time dependencies for this component. When tools are built, - the build system will include the transitive closer of + the build system will include the transitive closure of all required_libraries for the components the tool needs.

  • add_to_library_groups [optional]