The files in this directory:
Creates upper/lower case tests for testsuite.in.
Creates a Pike source distribution.
Locale extraction utility for the locate system
implemented in the Locale module.
Used by the build process to generate prototype header files to
enable dynamic load of libraries on Microsoft Windows.
Used by make depend to generate dependencies.
Alias for pike without arguments, which starts Hilfe,
the incremental Pike frontend.
Installs a Pike module into a pike module directory.
The Pike installation script, which is run when a
Pike is installed. It is also run by when a binary
export is made, to assemble the package it later will
Creates the file case_info.h during Pike build. The
case_info.h file is an optimized version of the case
information in the ../src/UnicodeData.txt file.
Creates the file interpret_functions_fixed.h during
Utility that permutates over a number of configure
flags and compiles and verifies all the produced Pikes.
Utility for creating executable installation scripts
based on Pike. [FIXME: Better description.]
Creates the file peep_engine.c during Pike build.
Generates testsuite files from testsuite.in files
during "make verify".
Creates the file mktreeopt.h during Pike build.
A simple script that fakes success for all configure
tests when --disable-binary is set.
[FIXME: What does this do? Doesn't appear to be called
from any Makefile.]
This file is generated from the file pike.in when make
all is built from the top level make file. This script
is a wrapper for the latest built Pike binary that
adds the posibility to start pike with the optional
argument --gdb to run the Pike in gdb. Usage example:
bin/pike --gdb program_that_crash.pike --arg arg2
The file from which the script pike is generated.
Creates .c files from .cmod files during Pike build.
The extremly handy "replace string in file" utility.
[FIXME: What does this do?]
Filters a tar file applying root/root ownership on
The program that performs the test suite when make
verify is run.
A GDB frontend for debugging pike code.
Generates a Xenofarm result package if run in a Xenofarm build
GDB commands that the Xenofarm client will run on any resulting core
files once its build and verification is done.