Skip to content
Snippets Groups Projects
Commit 692ab38b authored by Martin Stjernholm's avatar Martin Stjernholm
Browse files

Fixed some typos.

Rev: README-CVS:1.21
parent 408db9c0
No related branches found
No related tags found
No related merge requests found
$Id: README-CVS,v 1.20 2003/02/20 00:10:52 mast Exp $ $Id: README-CVS,v 1.21 2003/03/21 00:25:21 mast Exp $
HOW TO BUILD PIKE FROM CVS HOW TO BUILD PIKE FROM CVS
...@@ -60,35 +60,35 @@ depend Build the files that tracks dependencies between ...@@ -60,35 +60,35 @@ depend Build the files that tracks dependencies between
correct rebuilding if some of the source files correct rebuilding if some of the source files
change, but not if you only intend to use the change, but not if you only intend to use the
build tree once. It's not run by default. build tree once. It's not run by default.
source Prepare the source tree for compiliation without source Prepare the source tree for compilation without
the need for a preexisting installed pike. the need for a preexisting installed pike.
force_autoconfig Forces a build of the configure scripts. This is force_autoconfig Force a build of the configure scripts. This is
useful e.g. if a new module directory is added in useful e.g. if a new module directory is added in
the CVS. the CVS.
force_configure Forces configure to be run (recursively). If force_configure Force configure to be run (recursively). If
you've installed a new library and want pike to you've installed a new library and want pike to
detect it, then the simplest way is to remove detect it, then the simplest way is to remove
config.cache in the build directory (or perhaps config.cache in the build directory (or perhaps
just delete the relevant variables in it) and then just delete the relevant variables in it) and then
use this target. use this target.
dump_modules Dumps the Pike modules directly in the build tree. dump_modules Dump the Pike modules directly in the build tree.
That makes pike load faster if it's run directly That makes pike load faster if it's run directly
from there, e.g. through the bin/pike script (see from there, e.g. through the bin/pike script (see
below). These dumped modules are not used for below). These dumped modules are not used for
anything else. After this has been run once, any anything else. After this has been run once, any
changed Pike modules will be redumped changed Pike modules will be redumped
automatically by the main build targets. automatically by the main build targets.
undump_modules Removes any modules dumped by dump_modules, and undump_modules Remove any modules dumped by dump_modules, and
removes the redump step described above. remove the redump step described above.
force_dump_modules Forces all Pike modules to be redumped, not just force_dump_modules Force all Pike modules to be redumped, not just
those whose source files have changed. those whose source files have changed.
snapshot Create a snapshot export tarball. snapshot Create a snapshot export tarball.
export Create a source dist and bump up the build number export Create a source dist and bump up the build number
(if you have cvs write access). Please do not (if you have cvs write access). Please do not
check in the generated files. check in the generated files.
clean Removes all the built binary files. clean Remove all the built binary files.
cvsclean Removes all files that are generated automatically, cvsclean Remove all files that are generated automatically,
i.e. brings the tree back to the state as if it i.e. bring the tree back to the state as if it
was checked out from the CVS. was checked out from the CVS.
If you want to pass arguments to the configure script (see below), the If you want to pass arguments to the configure script (see below), the
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment