Changeset 29555
- Timestamp:
- Oct 25, 2010, 3:39:02 PM (16 years ago)
- Location:
- trunk
- Files:
-
- 1 added
- 6 edited
-
. (modified) (1 prop)
-
Changes.txt (added)
-
dbconfig (modified) (1 prop)
-
ippScripts (modified) (1 prop)
-
ippTasks (modified) (1 prop)
-
psconfig/INSTALL (modified) (5 diffs)
-
psconfig/tagsets/ipp-2.9.dist (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk
- Property svn:mergeinfo changed
-
trunk/dbconfig
- Property svn:mergeinfo changed
/branches/eam_branches/ipp-20100823/dbconfig (added) merged: 29515,29536
- Property svn:mergeinfo changed
-
trunk/ippScripts
- Property svn:mergeinfo changed
/branches/eam_branches/ipp-20100823/ippScripts (added) merged: 29124,29515,29536
- Property svn:mergeinfo changed
-
trunk/ippTasks
- Property svn:mergeinfo changed
/branches/eam_branches/ipp-20100823/ippTasks (added) merged: 29124,29515,29536
- Property svn:mergeinfo changed
-
trunk/psconfig/INSTALL
r26281 r29555 6 6 With the psconfig tools, it is easy to switch between different 7 7 installed versions or to recompile subsets of the IPP tree. 8 9 0. Choose a target installation directory.10 11 Choose a location to store the installed software and configuration12 files. The psconfig system places the installed binary files by13 default in directories below ~/psconfig. There will be one directory14 for each version of the installation for a given hardware15 architecture. To use a different location, place the following line16 in ~/.psconfigrc (otherwise, this is not needed):17 18 set PSCONFDIR = INSTALL_PATH19 20 where INSTALL_PATH is the top-level directory for all binary21 installations.22 8 23 9 1. Set up the psconfig system. … … 75 61 installation directories. 76 62 63 3. Building (full build in one pass) 64 65 It should be possible to build the full IPP installation by issuing 66 the single command in this directory (ipp/psconfig): 67 68 psbuild -extbuild 69 70 If you have checked the IPP tree out of our svn repository, certain 71 steps are slightly modified. In this case, it is necessary to add the 72 option '-dev'. For additional information on using psbuild, see the 73 listing of options below (or type psbuild -help) 74 75 psbuild -dev -extbuild 76 77 77 3. Dependencies 78 78 … … 112 112 pscheckperl -build 113 113 114 4. Building 114 4. Building (just IPP tools) 115 115 116 116 To build the full IPP tree using the psconfig system, run 'psbuild' in … … 123 123 option '-dev'. For additional information on using psbuild, see the 124 124 listing of options below (or type psbuild -help) 125 126 It should be possible to build the full IPP installation by issuing127 the single command in this directory (ipp/psconfig):128 129 psbuild -extbuild130 125 131 126 5. Building Magic. … … 180 175 pscheckperl -build : build and install external modules 181 176 177 ---- 178 0. Choose a target installation directory. 179 180 > Choose a location to store the installed software and configuration 181 > files. The psconfig system places the installed binary files by 182 > default in directories below ~/psconfig. There will be one directory 183 > for each version of the installation for a given hardware 184 > architecture. To use a different location, place the following line 185 > in ~/.psconfigrc (otherwise, this is not needed): 186 > 187 > set PSCONFDIR = INSTALL_PATH 188 > 189 > where INSTALL_PATH is the top-level directory for all binary 190 > installations. 191 192 ** the steps above are probably not actually needed. When is PSCONFDIR needed? 193 -
trunk/psconfig/tagsets/ipp-2.9.dist
r28486 r29555 80 80 YYYYY magic/censorObjects ipp-2-9 -0 81 81 YYYYY magic/remove ipp-2-9 -0 82 YYYYY console ipp-2-9 -0 82 83 83 84 # there are externally required C libraries and perl modules (see INSTALL)
Note:
See TracChangeset
for help on using the changeset viewer.
