Index: trunk/psconfig/INSTALL =================================================================== --- trunk/psconfig/INSTALL (revision 17403) +++ trunk/psconfig/INSTALL (revision 17404) @@ -7,18 +7,12 @@ installed versions or to recompile subsets of the IPP tree. -1. Set up the psconfig system. -1.1 csh users +0. Choose a target installation directory. -To use the psconfig system, place the following line in your ~/.cshrc -file: - -alias psconfig "source PATH/psconfig.csh" - -where PATH is the path to the file psconfig.csh in this directory -(ipp/psconfig/psconfig.csh). - -The psconfig system places the installed binary files by default in -directories below ~/psconfig. To use a different location, place the -following line in ~/.psconfigrc (otherwise not needed): +Choose a location to store the installed software and configuration +files. The psconfig system places the installed binary files by +default in directories below ~/psconfig. There will be one directory +for each version of the installation for a given hardware +architecture. To use a different location, place the following line +in ~/.psconfigrc (otherwise, this is not needed): set PSCONFDIR = INSTALL_PATH @@ -27,12 +21,37 @@ installations. -1.2 bash users +1. Set up the psconfig system. -Add the following line to your ~/.bashrc file: +If you have not previously installed the IPP suite, and do not the +psconfig scripts installed, you need to generate the scripts for your +install directory. Run the following command in this directory +(ipp/psconfig): -alias psconfig="source PATH/psconfig.bash" +psbuild -bootstrap INSTALL_PATH -it is also necessary to edit the file psconfig.bash to set the -PSCONFIG_DIR variable to this directory as well. +where INSTALL_PATH is the top-level directory for all binary +installations. Then, follow the instructions supplied by that +command: + +** if you use csh, tcsh or equivalent as your shell, add the following to your .cshrc + if (-e /home/kiawe/eugene/psconfig/psconfig.csh) then + alias psconfig "source /home/kiawe/eugene/psconfig/psconfig.csh" + else + alias psconfig "echo psconfig not available" + endif + psconfig default + +** if you use sh, bash or equivalent as your shell, add the following to your .bashrc + if [ -f /home/kiawe/eugene/psconfig/psconfig.csh ]; then + alias psconfig='source /home/kiawe/eugene/psconfig/psconfig.bash' + else + alias psconfig='echo psconfig not available' + fi + psconfig default + +Though, in your case, "/home/kiawe/eugene/psconfig/" will be replaced +by the value of INSTALL_PATH. After you have set up this alias, you +will need to source the .cshrc / .bashrc, or open a new shell, to have +these aliases available. 2. Using psconfig to set / examine your install system: @@ -55,4 +74,9 @@ 3. Dependencies +NOTE: It is possible to use the tools discussed below to manually check on the +external dependencies. However, the psbuild system now allows you to +build the full suite including dependencies in a single pass. To use +this method, skip to section 5. + 3.1. External C libraries @@ -64,5 +88,6 @@ at: -http://pan-starrs.ifa.hawaii.edu/project/IPP/software/ext +http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extlibs-2.5.tgz +http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extperl-2.5.tgz These should be installed so they will be available in the user's @@ -78,5 +103,5 @@ Perl modules, and can be used to install them in the appropriate user location in the psconfig system. The command defaults to the latest -perl installation table (eg, tagsets/ipp-1.2.perl). +perl installation table (eg, tagsets/ipp-2.5.perl). pscheckperl @@ -98,12 +123,49 @@ To build the full IPP tree using the psconfig system, run 'psbuild' in -this directory, and provide a distribution name. The distributions -define the set of IPP libraries and programs versions which go -together. NOTE: If we provide a tarball, it is appropriate to a -specific version. this should be automatically set as the default! +this directory: -psbuild ipp-1.2 +psbuild + +For additional information on using psbuild, see the listing of +options below (or type psbuild -help) + +5. Single-Pass Build with External Dependencies + +If you have not already done so, download the tarball with the +external libraries and perl modules from: + +http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extlibs-2.5.tgz +http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extperl-2.5.tgz + +It should be possible to build the full IPP installation by issuing +the single command in this directory (ipp/psconfig): + +psbuild -extbuild ------ + +More options for psbuild: + +USAGE: psbuild [options] (distribution) + : -version (version) : specify alternate psconfig installation version + : -verbose : give additional information + : -extlibs (tarball) : specify the location of the extlibs tarball + : -extperl (tarball) : specify the location of the extlibs tarball + : -extcheck : check (but do not build) the external dependencies + : -extbuild : check and build (if needed) the external dependencies + : -clean : clean the source directories before building + : -rebuild : run 'configure (and autogen for developer)' (C code) + : -optimize : set flags for optimized code + : -only (module) : only build the specified module + : -start (module) : begin build at specified module + : -stop (module) : stop build after specified module + + : -dev : build modules not distributed in tarball + + : psbuild -bootstrap : generate the psconfig scripts + : psbuild -list : list the available distributions + : psbuild -h : this help listing + : psbuild -help : this help listing + : psbuild --help : this help listing Summary of psconfig operations: