Table of Contents
The VR Juggler project uses the Autoconf utility to stay portable across platforms. This means you will have to “configure” the project before compiling it. To make sense of this documentation, please understand the concepts listed in the section called “Required Reading”. Posting about these subjects to the mailing list will probably be ignored.
In this chapter, the following conventions are used for text formatting and naming:
Program, file, and directory names are represented this way.
Commands that are intended to be run by the user are written in this style.
References to system and library calls are written as call_name(##) where “##” is the manual section where that call's documentation can be found.
Makefile targets are named as 'target', and makefile variables are named as $(VAR_NAME).
Environment variables are named as defined in the “Enviroment Variables” chapter in the Getting Started Guide.
When first downloading the Juggler source to compile it, users must generate the configure script and vjDefines.h.in template using autoconf and autoheader. This files are not part of the repository because they are generated using third-party tools from files in the repository (i.e., configure.in and acconfig.h). The usual way to generate the files is:
% ./autogen.sh
This must be executed in the top-level Juggler source directory.
Once the configure script is generated, it can be invoked by typing:
% ./configure.pl
To get a list of all available options for configure.pl, do:
% ./configure.pl --help
To get a list of all available options for the multitude of Autoconf-generated configure scripts, run:
% ./configure.pl --all-help