Changes between Version 6 and Version 7 of Building/Using


Ignore:
Timestamp:
Dec 7, 2007 3:44:47 PM (8 years ago)
Author:
vvv
Comment:

fix formatting errors: "\w—\w", "{{{[}]+$"

Legend:

Unmodified
Added
Removed
Modified
  • Building/Using

    v6 v7  
    5858backing up untold megabytes of easily-regenerated, and
    5959rapidly-changing, gubbins.  The golden rule is that (with a single
    60 exception - [[ref(Getting the build you want)]] ''absolutely
     60exception - [[ref(Getting the build you want)]]) ''absolutely
    6161everything in the build tree is either a symbolic link to the source
    6262tree, or else is mechanically generated''.  It should be perfectly OK
     
    199199keep a private directory of {{{build.mk}}} files, and use a symbolic
    200200link in each build tree to point to the appropriate one.)  So
    201 {{{mk/build.mk}}} never exists in the source tree—you create one
     201{{{mk/build.mk}}} never exists in the source tree — you create one
    202202in each build tree from the template.  We'll discuss what to put in it
    203203shortly.
     
    209209make variable definitions that override those in''
    210210{{{mk/config.mk.in}}}.  The whole point of
    211 {{{mk/config.mk.in}}}—and its derived counterpart
    212 {{{mk/config.mk}}}—is to define the build configuration. It is
     211{{{mk/config.mk.in}}} — and its derived counterpart
     212{{{mk/config.mk}}} — is to define the build configuration. It is
    213213heavily commented, as you will see if you look at it.  So generally,
    214214what you do is look at {{{mk/config.mk.in}}}, and add definitions in
     
    223223For example, {{{config.mk.in}}} contains the definition:
    224224
    225  {{{GhcHcOpts=-Rghc-timing}}}::
     225 {{{GhcHcOpts = -Rghc-timing}}}::
    226226  The accompanying comment explains that this is the list of flags
    227227  passed to GHC when building GHC itself.  For doing development, it
     
    322322make these changes take effect. In theory you should, however, say
    323323{{{make clean; make}}}, because configuration option changes could
    324 affect anything—but in practice you are likely to know what's
     324affect anything — but in practice you are likely to know what's
    325325affected.
    326326
     
    414414  [[br]][[br]]
    415415  Invoking the {{{boot}}} target explicitly is not normally necessary.
    416   From the top-level directory, invoking {{{make}}} causes {{{make
    417   boot}}} to be invoked in various subdirectories first, in the right
     416  From the top-level directory, invoking {{{make}}} causes {{{make boot}}}
     417  to be invoked in various subdirectories first, in the right
    418418  order.  Unless you really know what you are doing, it is best to
    419419  always say {{{make}}} from the top level first.
     
    454454  Delete all files from the current directory that are created by
    455455  configuring or building the program. If you have unpacked the source
    456   and built the program without creating any other files, {{{make
    457   distclean}}} should leave only the files that were in the
    458   distribution.
     456  and built the program without creating any other files, {{{make distclean}}}
     457  should leave only the files that were in the distribution.
    459458
    460459 {{{mostlyclean}}}::
     
    470469  One exception, however: {{{make maintainer-clean}}} should not
    471470  delete {{{configure}}} even if {{{configure}}} can be remade using a
    472   rule in the {{{Makefile}}}. More generally, {{{make
    473   maintainer-clean}}} should not delete anything that needs to exist
    474   in order to run {{{configure}}} and then begin to build the program.
     471  rule in the {{{Makefile}}}. More generally, {{{make maintainer-clean}}}
     472  should not delete anything that needs to exist in order to run
     473  {{{configure}}} and then begin to build the program.
    475474  [[br]][[br]]   
    476475  After a {{{maintainer-clean}}}, a {{{configure}}} will be necessary