haserl is a CGI wrapper that embeds a shell script in HTML documents.
Version: 0.8.0 / 0.9.24Haserl is a small cgi wrapper that enables shell scripts to be embedded into html documents. haserl is intended for environments where something like PHP is too big.
Operating System: Linux
It was written for Linux, but is known to run on FreeBSD. It compiles to around 10K, and a typical case is to use it to write cgi scripts run under a small web server, such as mini-httpd or thttpd.
Freely available under the terms of the GNU Public License (GPL2).
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions. Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, a file `config.cache' that saves the results of its tests to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it.
The file `configure.in' is used to create `configure' by a program called `autoconf'. You only need `configure.in' if you want to change it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute
Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with the package.
4. Type `make install' to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'.
There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that the `configure' script does not know about. You can give `configure' initial values for variables by setting them in the environment. Using a Bourne-compatible shell, you can do that on the command line like this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
What's New in 0.9.24 Development Release:
· Variables sent without an assigment (=) caused a segfault. (myscript.cgi?foo caused a script to abort early) (Scott)
· Several typos in the manpage were fixed (Scott)
· Scott's bash-extensions are included if configured with --enable-bash-extensions
· Running haserl with no args now reports if lua or the bash extensions are enabled.
· Form variables are now hardcoded to "FORM_*"
· Form varibles are now stored as FORM_ + GET_, POST_, COOKIE_ (scott) - WIP