build-instruction typos and clarifications

This commit is contained in:
Matthew Flatt 2020-12-27 19:08:19 -07:00
parent 8f05958ba2
commit 70a600e1b5
3 changed files with 9 additions and 7 deletions

View File

@ -368,8 +368,8 @@ repositorys top-level makefile and the `"distro-build"` package.
The `installers` target of the makefile will do everything to generate
installers: build a server on the current machine, run clients on hosts
specified via `CONFIG`, and start/stop VirtualBox virtual machines that
act as client machines.
specified via `CONFIG`, and start/stop VirtualBox virtual machines or
Docker containers that act as client machines.
If the server is already built, the `installers-from-built` target will
drive the client builds without re-building the server.
@ -392,7 +392,8 @@ build (not the one for building installers), you can use
  `make describe-clients CONFIG=my-site-config.rkt`
to see, without building anything, the effect of the configuration in
`"my-site-config.rkt"` and the planned build steps.
`"my-site-config.rkt"` and the planned build steps. See also the
`#:fake-installers?` site-configuration option.
The default `CONFIG` path is `"build/site.rkt"`, so you could put your
configuration file there and omit the `CONFIG` argument to `make`. A

View File

@ -36,7 +36,8 @@ Git repository's top-level makefile and @|distro-build-package|.
The @exec{installers} target of the makefile will do everything to
generate installers: build a server on the current machine, run
clients on hosts specified via @exec{CONFIG}, and start/stop
VirtualBox virtual machines that act as client machines.
VirtualBox virtual machines or Docker containers that act as client
machines.
If the server is already built, the @exec{installers-from-built}
target will drive the client builds without re-building the server.
@ -59,7 +60,8 @@ some Racket build (not the one for building installers), you can use
@commandline{make describe-clients CONFIG=my-site-config.rkt}
to see, without building anything, the effect of the configuration in
@filepath{my-site-config.rkt} and the planned build steps.
@filepath{my-site-config.rkt} and the planned build steps. See also the
@racket[#:fake-installers?] site-configuration option.
The default @exec{CONFIG} path is @filepath{build/site.rkt}, so you
could put your configuration file there and omit the @exec{CONFIG}

View File

@ -72,7 +72,6 @@ If you need more information specific to Racket BC, see
"bc/README.txt".
========================================================================
Compiling for supported Unix variants (including Linux)
========================================================================
@ -458,7 +457,7 @@ See also the shared sources below, which includes rktio, the macro
expander, and schemify.
Sources for the Racket BC implementation
-------------------------------------------------
----------------------------------------
* "bc" --- `racket` BC executable