This section describes all the targets related to installing VR Juggler from its source code. The targets are grouped together depending upon how they are related. For information on what is actually done as part of the full installation process, refer to the section called “Process of Full Install (Individual Steps)”. A current list of all the targets (with descriptions) can be found at the top of Makefile.in in the top-level Juggler source directory.
This target is the same as 'install-all'. It performas a full installation of library binaries (both debugging and optimized for the default ABI/ISA combination) and all associated files. The steps taken for this installation are as described in the section called “Process of Full Install (Individual Steps)”. This is the essentially second phase of the 'world' target described in Chapter 7. It requires that 'buildworld' be successfully completed beforehand.
This is the same as the 'installworld' target except that it installs all possible ABI and ISA combinations for the target platform. On IRIX, for example, this means that all combinations of N32, 64, mips3 and mips4 (debugging and optimized) are installed. Most platforms currently support only one ABI/ISA combination thus making this target exactly the same as 'installworld'. The steps taken for this installation follow those described in the section called “Process of Full Install (Individual Steps)”.
This target is the same as 'install'. It installs only the debugging version of the library binaries (both static and dynamic) and all associated files. It includes the combination of 'install-dbg' and 'install-ddso' (see below). The steps taken for this installation follow those described below. This is the target that is run when using the traditional make install command.
Install only the static debugging version of the library binaries. Nothing besides the libraries is installed.
Install only the dynamic debugging version of the library binaries. Nothing besides the libraries is installed.
Install only the optimized version of the library binaries (both static and dynamic) and all associated files. It includes the combination of 'install-opt' and 'install-dso' (see below). The steps taken for this installation follow those described in the section called “Process of Full Install (Individual Steps)”.
Install only the static optimized version of the library binaries. Nothing besides the libraries is installed.
Install only the dynamic optimized version of the library binaries. Nothing besides the libraries is installed.
Install all the header files from the VR Juggler source tree.
Install the sample applications and generate all the application makefiles from the Makefile.in templates. This makes a copy of the samples directory tree found in the VR Juggler source.
Install the test code and generate all the application makefiles from the Makefile.in templates. This makes a copy of the test directory tree found in the VR Juggler source.
Install the user tools and generate all the necessary makefiles from the Makefile.in templates. This makes a copy of the tools directory tree found in the VR Juggler source.
Install the standard VR Juggler data files. This makes a copy of the Data directory tree found in the VR Juggler source.
Install the VjControl JAR file and its runnable files. In a UNIX environment, the vjcontrol scripts are installed. On a Win32 platform, the vjcontrol.bat batch file is installed. This is done only if the configure script found a working Java compiler and the target is not being disabled via the $(NO_JAVA_GUI) variable.
Build the directory hierarchy for the installation. This is done before any of the “full” install targets ('installworld', 'install-all-abi', 'install-debug' and 'install-optim') is run. This is useful for testing parts of the installation or doing partial installations. Run it before doing any testing to create the full install hierarchy and then run the selected install targets. For example, to install only the static debugging libraries with nothing else, do:
make hier install-dbg