Changeset 17404
- Timestamp:
- Apr 8, 2008, 11:01:55 AM (18 years ago)
- File:
-
- 1 edited
-
trunk/psconfig/INSTALL (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/psconfig/INSTALL
r12926 r17404 7 7 installed versions or to recompile subsets of the IPP tree. 8 8 9 1. Set up the psconfig system. 10 1.1 csh users 9 0. Choose a target installation directory. 11 10 12 To use the psconfig system, place the following line in your ~/.cshrc 13 file: 14 15 alias psconfig "source PATH/psconfig.csh" 16 17 where PATH is the path to the file psconfig.csh in this directory 18 (ipp/psconfig/psconfig.csh). 19 20 The psconfig system places the installed binary files by default in 21 directories below ~/psconfig. To use a different location, place the 22 following line in ~/.psconfigrc (otherwise not needed): 11 Choose a location to store the installed software and configuration 12 files. The psconfig system places the installed binary files by 13 default in directories below ~/psconfig. There will be one directory 14 for each version of the installation for a given hardware 15 architecture. To use a different location, place the following line 16 in ~/.psconfigrc (otherwise, this is not needed): 23 17 24 18 set PSCONFDIR = INSTALL_PATH … … 27 21 installations. 28 22 29 1. 2 bash users23 1. Set up the psconfig system. 30 24 31 Add the following line to your ~/.bashrc file: 25 If you have not previously installed the IPP suite, and do not the 26 psconfig scripts installed, you need to generate the scripts for your 27 install directory. Run the following command in this directory 28 (ipp/psconfig): 32 29 33 alias psconfig="source PATH/psconfig.bash" 30 psbuild -bootstrap INSTALL_PATH 34 31 35 it is also necessary to edit the file psconfig.bash to set the 36 PSCONFIG_DIR variable to this directory as well. 32 where INSTALL_PATH is the top-level directory for all binary 33 installations. Then, follow the instructions supplied by that 34 command: 35 36 ** if you use csh, tcsh or equivalent as your shell, add the following to your .cshrc 37 if (-e /home/kiawe/eugene/psconfig/psconfig.csh) then 38 alias psconfig "source /home/kiawe/eugene/psconfig/psconfig.csh" 39 else 40 alias psconfig "echo psconfig not available" 41 endif 42 psconfig default 43 44 ** if you use sh, bash or equivalent as your shell, add the following to your .bashrc 45 if [ -f /home/kiawe/eugene/psconfig/psconfig.csh ]; then 46 alias psconfig='source /home/kiawe/eugene/psconfig/psconfig.bash' 47 else 48 alias psconfig='echo psconfig not available' 49 fi 50 psconfig default 51 52 Though, in your case, "/home/kiawe/eugene/psconfig/" will be replaced 53 by the value of INSTALL_PATH. After you have set up this alias, you 54 will need to source the .cshrc / .bashrc, or open a new shell, to have 55 these aliases available. 37 56 38 57 2. Using psconfig to set / examine your install system: … … 55 74 3. Dependencies 56 75 76 NOTE: It is possible to use the tools discussed below to manually check on the 77 external dependencies. However, the psbuild system now allows you to 78 build the full suite including dependencies in a single pass. To use 79 this method, skip to section 5. 80 57 81 3.1. External C libraries 58 82 … … 64 88 at: 65 89 66 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/ext 90 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extlibs-2.5.tgz 91 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extperl-2.5.tgz 67 92 68 93 These should be installed so they will be available in the user's … … 78 103 Perl modules, and can be used to install them in the appropriate user 79 104 location in the psconfig system. The command defaults to the latest 80 perl installation table (eg, tagsets/ipp- 1.2.perl).105 perl installation table (eg, tagsets/ipp-2.5.perl). 81 106 82 107 pscheckperl … … 98 123 99 124 To build the full IPP tree using the psconfig system, run 'psbuild' in 100 this directory, and provide a distribution name. The distributions 101 define the set of IPP libraries and programs versions which go 102 together. NOTE: If we provide a tarball, it is appropriate to a 103 specific version. this should be automatically set as the default! 125 this directory: 104 126 105 psbuild ipp-1.2 127 psbuild 128 129 For additional information on using psbuild, see the listing of 130 options below (or type psbuild -help) 131 132 5. Single-Pass Build with External Dependencies 133 134 If you have not already done so, download the tarball with the 135 external libraries and perl modules from: 136 137 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extlibs-2.5.tgz 138 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extperl-2.5.tgz 139 140 It should be possible to build the full IPP installation by issuing 141 the single command in this directory (ipp/psconfig): 142 143 psbuild -extbuild 106 144 107 145 ------ 146 147 More options for psbuild: 148 149 USAGE: psbuild [options] (distribution) 150 : -version (version) : specify alternate psconfig installation version 151 : -verbose : give additional information 152 : -extlibs (tarball) : specify the location of the extlibs tarball 153 : -extperl (tarball) : specify the location of the extlibs tarball 154 : -extcheck : check (but do not build) the external dependencies 155 : -extbuild : check and build (if needed) the external dependencies 156 : -clean : clean the source directories before building 157 : -rebuild : run 'configure (and autogen for developer)' (C code) 158 : -optimize : set flags for optimized code 159 : -only (module) : only build the specified module 160 : -start (module) : begin build at specified module 161 : -stop (module) : stop build after specified module 162 163 : -dev : build modules not distributed in tarball 164 165 : psbuild -bootstrap : generate the psconfig scripts 166 : psbuild -list : list the available distributions 167 : psbuild -h : this help listing 168 : psbuild -help : this help listing 169 : psbuild --help : this help listing 108 170 109 171 Summary of psconfig operations:
Note:
See TracChangeset
for help on using the changeset viewer.
