Changeset 26281
- Timestamp:
- Nov 25, 2009, 1:11:59 PM (16 years ago)
- File:
-
- 1 edited
-
trunk/psconfig/INSTALL (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/psconfig/INSTALL
r18977 r26281 77 77 3. Dependencies 78 78 79 NOTE: It is possible to use the tools discussed below to manually check on the80 external dependencies. However, the psbuild system now allows you to 81 build the full suite including dependencies in a single pass. To use82 this method, skip to section 5.79 NOTE: It is possible to use the tools discussed below to manually 80 check on the external dependencies. However, the psbuild system 81 allows you to build the full suite including dependencies in a single 82 pass. To use this method, skip to section 4. 83 83 84 84 3.1. External C libraries … … 88 88 libraries defined by LD_LIBRARY_PATH, and the installation library 89 89 defined by psconfig. Any missing dependencies will be listed. 90 Tarballs for these libraries may be found on the Pan-STARRS web site 91 at: 92 93 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extlibs-2.6.1.tgz 94 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extperl-2.6.1.tgz 95 96 These should be installed so they will be available in the user's 97 path. The psconfig commands can be used to install these libraries in 98 the psconfig location: 90 Tarballs for these libraries are included in the IPP software 91 distribution in the directory 'extlibs'. The command pschecklibs 92 -build can be used to install these libraries in the psconfig 93 location. Note that: 99 94 100 95 'psautogen' replaces autogen.sh … … 106 101 Perl modules, and can be used to install them in the appropriate user 107 102 location in the psconfig system. The command defaults to the latest 108 perl installation table (eg, tagsets/ipp-2. 6.1.perl).103 perl installation table (eg, tagsets/ipp-2.9.perl). 109 104 110 105 pscheckperl 111 106 112 will test for the perl modules specified for the latest ipp release. 113 if any modules are missing, they can be download from the Pan-STARRS 114 web site: 115 116 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extperl 117 118 The tarballs should be placed in a directory extperl parallel to the 119 ipp directory (two levels up from this directory). If the tarballs 120 are in the correct location, they can be built by supplying the -build 107 will test for the perl modules specified for the latest IPP release. 108 The (known) IPP-required Perl modules are included in the IPP software 109 distribution in 'extperl', and can be built by supplying the -build 121 110 flag to pscheckperl: 122 111 … … 130 119 psbuild 131 120 132 For additional information on using psbuild, see the listing of 133 options below (or type psbuild -help) 134 135 5. Single-Pass Build with External Dependencies 136 137 If you have not already done so, download the tarball with the 138 external libraries and perl modules from: 139 140 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extlibs-2.6.1.tgz 141 http://pan-starrs.ifa.hawaii.edu/project/IPP/software/extperl-2.6.1.tgz 121 If you have checked the IPP tree out of our svn repository, certain 122 steps are slightly modified. In this case, it is necessary to add the 123 option '-dev'. For additional information on using psbuild, see the 124 listing of options below (or type psbuild -help) 142 125 143 126 It should be possible to build the full IPP installation by issuing … … 145 128 146 129 psbuild -extbuild 130 131 5. Building Magic. 132 133 The Magic software, required for processing of PS1/GPC1 data before it 134 can be released to the community, is not generally available for 135 distribution. For those without access to this software, the psbuild 136 will simply skip the step of building the magic software. For those 137 who have access to this software, it is necessary to install the magic 138 source code in the IPP tree before building. The magic and 139 ssa-core-cpp tarballs must be placed in the home directory. Go to the 140 magic directory (cd ../magic) and run the command 'make update'. This 141 will untar the magic code into the local magic directory and install 142 an appropriately modified makefile. Return to this directory and 143 follow the build instructions as above. (NOTE: this step is only 144 necessary for a new IPP checkout or a new magic tarball). 147 145 148 146 ------
Note:
See TracChangeset
for help on using the changeset viewer.
