pike.git / README-GIT

version» Context lines:

pike.git/README-GIT:2:   HOW TO BUILD PIKE FROM GIT      If you like to live at the bleeding edge you can download Pike from   git 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.      Keep in mind that the git versions are under heavy development and - have not been tested nearly as well as the offcial releases. You use - the code AT YOUR OWN RISK. + have not been tested nearly as well as the official releases. You + use the code AT YOUR OWN RISK.         DEPENDENCIES      Building from git requires the same tools as building from a source   distribution (gnu m4, bison and a C compiler, suggested also GNU make   and libz), and then some. In addition to thosee requirements, you   need a working Pike, autoconf and gcc (to generate the dependency   files; another compiler can be used to do the actual compilation).   
pike.git/README-GIT:89:   gitclean Remove all files that are generated automatically,    i.e. bring the tree back to the state as if it    was checked out from the git.         CONFIGURE OPTIONS AND BUILD VARIABLES      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" +  make CONFIGUREARGS="--prefix=/usr/local/my-pike --with-debug"      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   change them later if you like. There's a special case for the --help   argument: If CONFIGUREARGS is set to '--help' then the help text from   the configure script is shown and nothing else is done, and the stored   CONFIGUREARGS setting isn't affected.      The build targets also creates a script 'pike' in the bin subdirectory
pike.git/README-GIT:111:   you want to use Pike this way (which is mainly useful if you update   from git often), you should consider doing 'make dump_modules' to make   it start faster.         Some options for the configure script are:      --prefix=/foo/bar if you want to install Pike in /foo/bar,    default is /usr/local.   --without-gdbm compile without gdbm support - --without-bignums disable support for large integers - --without-gmp compile without gmp support (implies -  --without-bignums) +    --with-rtldebug compile with runtime debug checks   --without-cdebug compile without debug symbols (-g)   --with-debug same as --with-rtldebug --with-cdebug   --without-debug same as --without-rtldebug --without-cdebug   --without-copt compile without -O2   --without-threads compile without threads support (see    also the section 'If It Doesn't Work' below)   --without-zlib compile without gzip compression libary    support   --without-dynamic-modules compile statically, no dynamic loading    used (makes the binary larger)   --without-mysql compile without mysql support   --with-profiling enables profiling Pike code but slows    down interpreter a little   --with-poll use poll instead of select   --with-dmalloc compile with memory tracking, makes Pike    very slow, use for debugging only. - --with-security enable internal object security system +          You might also want to set the following environment variables:      CFLAGS Put extra flags for your C compiler here.   CPPFLAGS Put extra flags for your C preprocessor here    (such as -I/usr/gnu/include)   LDFLAGS Put extra flags to your linker here, such as    -L/usr/gnu/lib and -R/usr/gnu/lib