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

More info on Makefile targets. Removed tabs to ensure that the file

looks ok when viewed in broken editors.

Rev: README-CVS.txt:1.19
parent 3d5cbad9
Branches
Tags
No related merge requests found
$Id: README-CVS.txt,v 1.18 2002/04/11 15:57:19 mast Exp $ $Id: README-CVS.txt,v 1.19 2002/07/24 14:09:47 mast Exp $
HOW TO BUILD PIKE FROM CVS HOW TO BUILD PIKE FROM CVS
...@@ -43,23 +43,54 @@ files. ...@@ -43,23 +43,54 @@ files.
Other interesting make targets are: Other interesting make targets are:
install compile and install in default location install Compile and install in default location.
install_interactive interactive install install_interactive Interactive install.
tinstall test install, i.e. install in build directory tinstall Test install, i.e. install in build directory.
verify run the testsuite verify Do a test install and run the testsuite with the
run_hilfe run hilfe without installing pike installed pike.
documentation build the reference documentation from the just_verify Run the testsuite directly with the pike binary in
the build tree.
run_hilfe Run hilfe without installing pike.
pike Build only the pike core, do not recurse into the
module directories.
documentation Build the reference documentation from the
source. See the refdoc subdirectory. source. See the refdoc subdirectory.
source prepare the source tree for compiliation without depend Build the files that tracks dependencies between
the need for a Pike. the source files. This is necessary to ensure
snapshot create a snapshot export tarball. correct rebuilding if some of the source files
export create a source dist and bump up the build number change, but not if you only intend to use the
(if you have cvs write access). Please DO NOT build tree once. It's not run by default. See
also the note below about this target.
source Prepare the source tree for compiliation without
the need for a preexisting installed pike.
force_autoconfig Forces a build of the configure scripts. This is
useful e.g. if a new module directory is added in
the CVS.
force_configure Forces configure to be run (recursively). If
you've installed a new library and want pike to
detect it, then the simplest way is to remove
config.cache in the build directory (or perhaps
just delete the relevant variables in it) and then
use this target.
dump_modules Dumps the Pike modules directly in the build tree.
That makes pike load faster if it's run directly
from there, e.g. through the bin/pike script (see
below). These dumped modules are not used for
anything else. After this has been run once, any
changed Pike modules will be redumped
automatically by the main build targets.
undump_modules Removes any modules dumped by dump_modules, and
removes the redump step described above.
force_dump_modules Forces all Pike modules to be redumped, not just
those whose source files have changed.
snapshot Create a snapshot export tarball.
export Create a source dist and bump up the build number
(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 Removes all the built binary files.
cvsclean removes all files that are generated automatically, cvsclean Removes all files that are generated automatically,
i.e. brings the tree back to the state as if it i.e. brings the tree back to the state as if it
were 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
simplest way is to use the CONFIGUREARGS variable, like this: simplest way is to use the CONFIGUREARGS variable, like this:
...@@ -80,6 +111,16 @@ you want to use Pike this way (which is mainly useful if you update ...@@ -80,6 +111,16 @@ you want to use Pike this way (which is mainly useful if you update
from CVS often), you should consider doing 'make dump_modules' to make from CVS often), you should consider doing 'make dump_modules' to make
it start faster. it start faster.
Note about the depend target: Dependencies are typically between *.c
files and the *.h files they include. Since many *.c files are
generated from other input, the depend target often trigs other
targets to generate them. Some of those targets use the pike binary
in the build tree, so if you do make depend before pike is first built
in a new build tree, you're likely to end up building everything.
That can seem like a bit of catch 22, but since the dependency files
are only needed to correctly rebuild in an old tree, it's perfectly ok
to wait with make depend until you have built Pike once.
CONFIGURE OPTIONS AND BUILD VARIABLES CONFIGURE OPTIONS AND BUILD VARIABLES
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment