Build Instructions

Extracting archive

The product archive can be extracted to any desired directory using unzip (.zip file extension) or gunzip (.gz file extension)/ bunzip2 (.bz2 file extension) and tar. After extracting, the following directories will be created:

Table 1. Directory Structure.

Directory	Description
prolinga-web-0.0.2	Product version root directory.
prolinga-web-0.0.2/config	Config build information.
prolinga-web-0.0.2/doc	Documentation.
prolinga-web-0.0.2/src	All source and internal header files.
prolinga-web-0.0.2/tests	Self tests.
prolinga-web-0.0.2/prolinga	Raw configuration files.

Compiling and Linking

To build the product go to the product root directory and run the configure script. For default installation in /usr/local type:

./configure

To install into another directory type:

./configure --prefix=/any/dirname/

To compile as traditional instead of FastCGI:

./configure --disable-fastcgi

To link against the ProLinga-4GL language interpreter and run-time environment, type:

./configure --enable-run

For all other configure options, type:

./configure --help

After running the configure script, the product can be build with:

make

To run the optional self-test type:

make check

After compilation, the binaries, libraries and header files can be installed with:

make install

You may need root access for this last option.

By default, HTML documentation pages are available in the doc/html directory. These pages are generated from DocBook XML file format files in /doc. To re-generate the HTML pages from these files type:

make html

The command line XSLT processor xsltproc must be available from $PATH to be able to generate the HTML documentation.

Dependencies

Many of the ProLinga Projects are dependent on 3rd party libraries. These (non system) dependencies of ProLinga-Validate are outlined below. If these 3rd party products are not installed in either /usr/bin, /usr/lib, /usr/include or /usr/local/bin, /usr/local/lib, /usr/local/include, the additional configure option needs to be provided when building.

Table 2. Dependencies

Dependency	Version	Configure Option
libxml2	>=2.6.31	--with-libxml-prefix=`/path/to/libxml2`
libxslt	>=1.1.22	--with-libxslt-prefix=`/path/to/libxslt`
ProLinga-Run	>=0.0.1	--with-prolingarun-prefix=`/path/to/prolingarun`
ProLinga-Soap	>=0.0.1	--with-prolingasoap-prefix=`/path/to/prolingasoap`

Choosing the right type of build

The default configuration options provide libraries which can be used both to develop/debug as to run the product. However better builds are possible for a dedicated development or production environment.

In production environments, builds are needed which contain minimal (debug) overhead, so they are fast and small. To build such binaries/libraries, the --enable-final options can be used. Example:

./configure --enable-final

The enable-final flag is configured to be used with GCC environments only. If access to more compilers become available over time, the enable-flag will be ported to those compilers as well.

In development environments, builds are needed producing warnings, enabling maximum debugging info etc. Several options are available here.

--disable-fastcgi : Compile as traditional instead of FastCGI
--enable-warnings : Set all compiler warning flags
--enable-debug : Enable all debug messages
--enable-gprof : Enables profiling with gprof (GCC only)