Changes between Version 7 and Version 8 of Building/Using

Timestamp:

01/06/08 18:42:59 (5 years ago)

Author:

wkahl

Comment:

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

Building/Using

@@ -46 +46 @@
 copy of the source file.  There are "standard" Unix utilities that
 make such copies, so standard that they go by different names:
-{{{lndir}}} {{{mkshadowdir}}} are two (If you don't have either, the
+{{{lndir}}} and {{{mkshadowdir}}} are two (If you don't have either, the
 source distribution includes sources for the X11
 {{{lndir}}} - check out {{{utils/lndir}}}). See 
@@ -199 +199 @@
 keep a private directory of {{{build.mk}}} files, and use a symbolic
 link in each build tree to point to the appropriate one.)  So
-{{{mk/build.mk}}} never exists in the source tree — you create one
+{{{mk/build.mk}}} never exists in the source tree — you create one
 in each build tree from the template.  We'll discuss what to put in it
 shortly.
@@ -209 +209 @@
 make variable definitions that override those in''
 {{{mk/config.mk.in}}}.  The whole point of
-{{{mk/config.mk.in}}} — and its derived counterpart
-{{{mk/config.mk}}} — is to define the build configuration. It is
+{{{mk/config.mk.in}}} — and its derived counterpart
+{{{mk/config.mk}}} — is to define the build configuration. It is
 heavily commented, as you will see if you look at it.  So generally,
 what you do is look at {{{mk/config.mk.in}}}, and add definitions in
@@ -322 +322 @@
 make these changes take effect. In theory you should, however, say
 {{{make clean; make}}}, because configuration option changes could
-affect anything — but in practice you are likely to know what's
+affect anything — but in practice you are likely to know what's
 affected.