Changes between Version 7 and Version 8 of Building/Using


Ignore:
Timestamp:
Jan 7, 2008 2:42:59 AM (8 years ago)
Author:
wkahl
Comment:

Inserted an and and turned HTML mdash entities into emdash characters.

Legend:

Unmodified
Added
Removed
Modified
  • Building/Using

    v7 v8  
    4646copy of the source file.  There are "standard" Unix utilities that
    4747make such copies, so standard that they go by different names:
    48 {{{lndir}}} {{{mkshadowdir}}} are two (If you don't have either, the
     48{{{lndir}}} and {{{mkshadowdir}}} are two (If you don't have either, the
    4949source distribution includes sources for the X11
    5050{{{lndir}}} - check out {{{utils/lndir}}}). See
     
    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
     
    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