pike.git / README-CVS

version» Context lines:

pike.git/README-CVS:1: - $Id: README-CVS,v 1.19 2002/12/05 17:31:21 nilsson fake $ + $Id: README-CVS,v 1.20 2003/03/21 00:25:21 mast Exp $         HOW TO BUILD PIKE FROM CVS      If you like to live at the bleeding edge you can download pike from CVS   with all the latest additions from the developers. There are two   major branches in the archive, the latest stable branch and latest   development branch. Stable versions have an even minor version number,   i.e. 7.0.x, 7.2.x, 7.4.x, whereas the development branches have an odd   minor version.
pike.git/README-CVS:54:   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.   depend Build the files that tracks dependencies between    the source files. This is necessary to ensure    correct rebuilding if some of the source files    change, but not if you only intend to use the    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 + source Prepare the source tree for compilation without    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    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    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. + dump_modules Dump 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 + undump_modules Remove any modules dumped by dump_modules, and +  remove the redump step described above. + force_dump_modules Force 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. - clean Removes all the built binary files. - cvsclean Removes all files that are generated automatically, -  i.e. brings the tree back to the state as if it + clean Remove all the built binary files. + cvsclean Remove all files that are generated automatically, +  i.e. bring the tree back to the state as if it    was checked out from the CVS.      If you want to pass arguments to the configure script (see below), the   simplest way is to use the CONFIGUREARGS variable, like this:       make CONFIGUREARGS="--prefix=/usr/local/my-pike --with-security"      The arguments passed through CONFIGUREARGS are remembered in the build   tree and reused if CONFIGUREARGS is undefined or the empty string.   You therefore don't need to repeat them every time, but you can still