Changes between Version 12 and Version 13 of Attic/Building/BuildSystem


Ignore:
Timestamp:
Oct 9, 2006 1:51:38 PM (9 years ago)
Author:
alexey
Comment:

xrefs && paragraph level after nested list

Legend:

Unmodified
Added
Removed
Modified
  • Attic/Building/BuildSystem

    v12 v13  
    196196      tell {{{make}}} how to construct one file 
    197197      from another. 
    198    [[br]] 
    199    {{{boilerplate.mk}}} needs to be 
    200    {{{include}}}d at the ''top'' 
    201    of each {{{Makefile}}}, so that the user can 
    202    replace the boilerplate definitions or pattern rules by 
    203    simply giving a new definition or pattern rule in the 
    204    {{{Makefile}}}.  {{{make}}} 
    205    simply takes the last definition as the definitive one. 
    206    [[br]][[br]] 
    207    Instead of ''replacing'' boilerplate 
    208    definitions, it is also quite common to 
    209    ''augment'' them. For example, a 
    210    {{{Makefile}}} might say: 
    211    {{{ 
     198 
     199  {{{boilerplate.mk}}} needs to be 
     200  {{{include}}}d at the ''top'' 
     201  of each {{{Makefile}}}, so that the user can 
     202  replace the boilerplate definitions or pattern rules by 
     203  simply giving a new definition or pattern rule in the 
     204  {{{Makefile}}}.  {{{make}}} 
     205  simply takes the last definition as the definitive one. 
     206  [[br]][[br]] 
     207  Instead of ''replacing'' boilerplate 
     208  definitions, it is also quite common to 
     209  ''augment'' them. For example, a 
     210  {{{Makefile}}} might say: 
     211  {{{ 
    212212SRC_HC_OPTS += -O 
    213213}}} 
    214    thereby adding "{{{-O}}}" to 
    215    the end of 
    216    {{{SRC_HC_OPTS}}}. 
     214  thereby adding "{{{-O}}}" to 
     215  the end of 
     216  {{{SRC_HC_OPTS}}}. 
    217217 
    218218 * {{{target.mk}}} contains 
     
    274274 
    275275is the build configuration file we discussed at 
    276 length in <xref linkend="sec-build-config"/>. 
     276length in [wiki:Building/Using#Gettingthebuildyouwant getting the build you want]. 
    277277 
    278278 
     
    406406{{{HC_OPTS}}}, 
    407407the option strings to pass to the Haskell compiler.  See 
    408 <xref linkend="sec-suffix"/>. 
     408[[ref(Pattern rules and options)]]. 
    409409 
    410410 
    411411=== {{{suffix.mk}}} === 
    412412 
    413 defines standard pattern rules--see <xref 
    414 linkend="sec-suffix"/>. 
     413defines standard pattern rules--see [[ref(Pattern rules and options)]]. 
    415414 
    416415       
     
    456455which will generate intermediate .hc files to port to the target 
    457456architecture for bootstrapping.  The libraries and stage 2 compiler 
    458 will be built as HC files for the target system (see <xref 
    459 linkend="sec-porting-ghc" /> for details. 
     457will be built as HC files for the target system (see [wiki:Building/Porting Porting GHC] for details). 
    460458 
    461459More details on when to use BUILD, HOST or TARGET can be found in 
     
    530528   {{{WAY_CC_OPTS}}} holds 
    531529   options to pass to the C compiler when compiling the 
    532    standard way.  (<xref linkend="sec-ways"/> dicusses 
     530   standard way.  ([[ref(Way management)]] dicusses 
    533531   multi-way compilation.) 
    534532 
     
    713711   want these targets built for.  The mechanism here is very 
    714712   much like the recursive invocation of 
    715    {{{make}}} in sub-directories (<xref 
    716    linkend="sec-subdirs"/>).  It is up to you to set 
     713   {{{make}}} in sub-directories ([[ref(Recursion)]]). 
     714   It is up to you to set 
    717715   {{{WAYS}}} in your 
    718716   {{{Makefile}}}; this is how you control what