*** Copyright (c) SRI International 2002. *** There are two basic steps to install SAL2XML: 1. Configure SAL2XML by running the `configure' script. You may want to pass some options to it, see below. 2. Install SAL2XML by running `make install'. Generic instructions for configuring and compiling auto-configured packages are included below. Here is an illustration of commands that might be used to build and install SAL2XML. The actual configuration, and installation output is not shown. % tar xvfz sal2xml-1.0.tar.gz # unpack the sources % cd sal2xml-1.0 # change to the toplevel directory % ./configure # run the `configure' script % make install # install SAL2XML The `configure' script examines your system, and adapts SAL2XML to run on it. The script has many options, some of which are described in the generic instructions included at the end of this file. All of the options can be listed using the command `./configure --help'. The `make install' commands installs SAL2XML executables, man pages, etc. After running `make install' and assuming the build process was successful you should be able to run `sal2xml'. If you want to force a specific JAVA compiler/virtural machine, you can use the following command line: % ./configure JAVAC= JAVA= Example: % ./configure JAVAC=javac JAVA=java If you want to recompile the SAL parser you should use: % ./configure --enable-build % make The `make' command builds the program. The parser generator produces several warning messages, you should ignore them. When ./configure fails ================================== If you are sure that this library is correctly installed, but configure fails to detect them, the following might help: Set your CLASSPATH environment variable to look for the library in a certain place, e.g. if you are working in a bash shell you would say: export CLASSPATH=:$CLASSPATH before you run configure. It's wise to remove the file 'config.cache' before re-running configure. The `configure' script uses environment variable JAVAC (JAVA) then tests in sequence various common Java compilers (virtual machines). For political reasons, it starts with the free ones. If you want to force a specific JAVA compiler (virtural machine), you can use the following command line: % ./configure JAVAC= JAVA= Generic Instructions for Building Auto-Configured Packages ========================================================== To compile this package: 1. Configure the package for your system. In the directory that this file is in, type `./configure'. 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 `configure' itself. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation, and creates the Makefile(s) (one in each subdirectory of the source directory). In some packages it creates a C header file containing system-dependent definitions. It also creates a file `config.status' that you can run in the future to recreate the current configuration. Running `configure' takes a minute or two. To compile the package in a different directory from the one containing the source code, you must use GNU make. `cd' to the directory where you want the object files and executables to go and run `configure' with the option `--srcdir=DIR', where DIR is the directory that contains the source code. Using this option is actually unnecessary if the source code is in the parent directory of the one in which you are compiling; `configure' automatically checks for the source code in `..' if it does not find it in the current directory. By default, `make install' will install the package's files in /usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can specify an installation prefix other than /usr/local by giving `configure' the option `--prefix=PATH'. You can specify separate installation prefixes for machine-specific files and machine-independent files. If you give `configure' the option `--exec-prefix=PATH', the package will use PATH as the prefix for installing programs and libraries. Normally, all files are installed using the same prefix. `configure' ignores any other arguments that you give it. If your system requires unusual options for compilation or linking that `configure' doesn't know about, you can give `configure' initial values for some variables by setting them in the environment. In Bourne-compatible shells, you can do that on the command line like this: CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure The `make' variables that you might want to override with environment variables when running `configure' are: (For these variables, any value given in the environment overrides the value that `configure' would choose:) CC C compiler program. Default is `cc', or `gcc' if `gcc' is in your PATH. INSTALL Program to use to install files. Default is `install' if you have it, `cp' otherwise. INCLUDEDIR Directory for `configure' to search for include files. Default is /usr/include. (For these variables, any value given in the environment is added to the value that `configure' chooses:) DEFS Configuration options, in the form '-Dfoo -Dbar ...' LIBS Libraries to link with, in the form '-lfoo -lbar ...' If you need to do unusual things to compile the package, we encourage you to teach `configure' how to do them and mail the diffs to the address given in the README so we can include them in the next release. 2. Type `make' to compile the package. 3. Type `make install' to install programs, data files, and documentation. 4. You can remove the program binaries and object files from the source directory by typing `make clean'. To also remove the Makefile(s), the header file containing system-dependent definitions (if the package uses one), and `config.status' (all the files that `configure' created), type `make distclean'. The file `configure.in' is used as a template to create `configure' by a program called `autoconf'. You will only need it if you want to regenerate `configure' using a newer version of `autoconf'.