- Timestamp:
- 03/24/2007 04:24:26 PM (17 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 1d359cd
- Parents:
- f9950ee
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
pst/ps/fop.xml
rf9950ee r492000e 5 5 %general-entities; 6 6 7 <!-- Inserted as a reminder to do this. The mention of a test suite 8 is usually right before the root user installation commands. Please 9 delete these 12 (including one blank) lines after you are done.--> 10 11 <!-- Use one of the two mentions below about a test suite, 12 delete the line that is not applicable. Of course, if the 13 test suite uses syntax other than "make check", revise the 14 line to reflect the actual syntax to run the test suite --> 15 16 <!-- <para>This package does not come with a test suite.</para> --> 17 <!-- <para>To test the results, issue: <command>make check</command>.</para> --> 18 19 <!ENTITY fop-download-http "http://apache.mirrors.pair.com/xml/fop/source/fop-&fop-version;-src.tar.gz"> 20 <!ENTITY fop-download-ftp "ftp://apache.mirrors.pair.com/xml/fop/source/fop-&fop-version;-src.tar.gz"> 21 <!ENTITY fop-md5sum "1a31eb1357e5d4b8d32d4cb3edae2da2"> 22 <!ENTITY fop-size "7.8 MB"> 23 <!ENTITY fop-buildsize "47.9 MB"> 24 <!ENTITY fop-time "0.25 SBU"> 7 <!ENTITY fop-download-http "http://apache.mirrors.pair.com/xmlgraphics/fop/fop-&fop-version;-src.tar.gz"> 8 <!ENTITY fop-download-ftp "ftp://apache.mirrors.pair.com/xmlgraphics/fop/fop-&fop-version;-src.tar.gz"> 9 <!ENTITY fop-md5sum "184c578a6269a8287ed150e0fc12868d"> 10 <!ENTITY fop-size "11.7 MB"> 11 <!ENTITY fop-buildsize "216 MB"> 12 <!ENTITY fop-time "0.9 SBU"> 25 13 26 14 <!ENTITY jai-download "http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=22&PartDetailId=jai-1_1_2_01-oth-JPR&SiteId=JSC&TransactionId=noreg"> 27 15 <!ENTITY jai-md5sum "f2be3619a8d002eff3874355e96327eb"> 28 16 <!ENTITY jai-size "2.6 MB"> 17 18 <!ENTITY offo-download "http://downloads.sourceforge.net/offo/offo-hyphenation.zip"> 19 <!ENTITY offo-md5sum "0b8c1657ef70285ad7fd514061b08c3e"> 20 <!ENTITY offo-size "359 KB"> 29 21 ]> 30 22 … … 79 71 80 72 <itemizedlist spacing="compact"> 81 <title>Required package</title> 82 <listitem> 83 <para><application>Java</application> Advanced Imaging (JAI) API 84 components: <ulink url="&jai-download;"> 85 http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=22&</ulink> 86 <ulink url="&jai-download;"> 87 PartDetailId=jai-1_1_2_01-oth-JPR&SiteId=JSC&TransactionId=noreg</ulink> 73 <title>Required packages</title> 74 <listitem> 75 <para>Objects for Formatting Objects (OFFO) hyphenation patterns: 76 <simplelist> 77 <member><ulink url="&offo-download;"/></member> 78 <member>&offo-md5sum;</member> 79 <member>&offo-size;</member> 80 </simplelist> 88 81 </para> 89 82 </listitem> 90 83 <listitem> 91 <para>Download MD5 sum: &jai-md5sum;</para> 92 </listitem> 93 <listitem> 94 <para>Download size: &jai-size;</para> 84 <para>Java Advanced Imaging (JAI) API components: 85 <simplelist> 86 <member> 87 <ulink url="&jai-download;"> 88 http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=22&</ulink> 89 <ulink url="&jai-download;"> 90 PartDetailId=jai-1_1_2_01-oth-JPR&SiteId=JSC&TransactionId=noreg</ulink> 91 </member> 92 <member>&jai-md5sum;</member> 93 <member>&jai-size;</member> 94 <member>Choose the <quote>Linux JDK Install</quote> file after 95 accepting the license agreement.</member> 96 </simplelist> 97 </para> 95 98 </listitem> 96 99 </itemizedlist> 97 100 98 <para>Choose the <quote><application>Linux</application> 99 <application>JDK</application> Install</quote> file after 100 accepting the license agreement.</para> 101 102 <itemizedlist spacing='compact'> 101 <!-- <itemizedlist spacing='compact'> 103 102 <title>Required patch</title> 104 103 <listitem> … … 106 105 url="&patch-root;/fop-&fop-version;-jdk_1.5.0-1.patch"/></para> 107 106 </listitem> 108 </itemizedlist> 107 </itemizedlist> --> 109 108 110 109 <bridgehead renderas="sect3">FOP Dependencies</bridgehead> 111 110 112 111 <bridgehead renderas="sect4">Required</bridgehead> 113 <para role="required"><xref linkend=" jdk"/></para>112 <para role="required"><xref linkend="apache-ant"/></para> 114 113 115 114 <bridgehead renderas="sect4">Optional</bridgehead> 116 <para role="optional"><xref linkend="libxslt"/>, 117 <ulink url="http://java.sun.com/products/jimi/">JIMI SDK</ulink>, 118 <ulink url="http://xml.apache.org/batik/">Batik</ulink> and 115 <para role="optional"><ulink url="http://java.sun.com/products/jimi/">JIMI SDK</ulink>, 116 <ulink url="http://xmlunit.sourceforge.net/">XMLUnit</ulink>, and 119 117 <ulink url="http://forrest.apache.org/">Forrest</ulink> (only used to rebuild 120 118 the documentation)</para> … … 128 126 <title>Installation of FOP</title> 129 127 130 <note> 131 <para>Ensure <envar>$JAVA_HOME</envar> is set correctly before beginning 132 the build.</para> 133 </note> 134 135 <para>Some versions of tar will display a message similar to 128 <para>Ensure <envar>$JAVA_HOME</envar> is set correctly before beginning 129 the build. To build the <application>JIMI SDK</application> and/or 130 <application>XMLUnit</application> extension classes, ensure the 131 corresponding <filename class='extension'>.jar</filename> files are 132 identified in the <envar>CLASSPATH</envar> environment variable.</para> 133 134 <!-- <para>Some versions of tar will display a message similar to 136 135 <quote><computeroutput>tar: A lone zero block at 33476</computeroutput></quote> 137 when unpacking the source tarball. You may safely ignore this message.</para> 136 when unpacking the source tarball. You may safely ignore this message.</para> --> 137 138 <sect3> 139 <title>Installing OFFO Hyphenation Patterns</title> 140 141 <para>Before beginning the build, unpack the 142 <application>FOP</application> source tarball and the hyphenation zipfile 143 from the same directory, then change directories into the root of the 144 <application>FOP</application> source tree. The XML Hyphenation patterns 145 will be copied into the <application>FOP</application> source tree by 146 running the following commands:</para> 147 148 <screen><userinput>cp ../offo-hyphenation/hyph/* hyph && 149 rm -rf ../offo-hyphenation</userinput></screen> 150 151 </sect3> 138 152 139 153 <sect3> … … 141 155 142 156 <tip> 143 <para>The 144 <command>$FOP_BUILD_DIR/jai-1_1_2_01-lib-linux-i586-jdk.bin</command> 157 <para>The <command>$FOP_BUILD_DIR/JAI.bin</command> 145 158 command below installs the JAI components in the JDK tree. You will be 146 159 required to view, and then accept (by entering a <keycap>y</keycap> … … 157 170 root of the <application>FOP</application> source tree:</para> 158 171 159 <screen role="root"><userinput>cp ../jai-1_1_2_01-lib-linux-i586-jdk.bin . && 160 sed -i 's/tail +122/tail -n +122/' \ 161 jai-1_1_2_01-lib-linux-i586-jdk.bin && 162 chmod 755 jai-1_1_2_01-lib-linux-i586-jdk.bin && 172 <screen role="root"><userinput>install -m755 ../jai-1_1_2_01-lib-linux-i586-jdk.bin JAI.bin && 173 sed -i 's/tail +122/tail -n +122/' JAI.bin && 174 163 175 FOP_BUILD_DIR=$(pwd) && 164 176 cd $JAVA_HOME && 165 $FOP_BUILD_DIR/jai-1_1_2_01-lib-linux-i586-jdk.bin && 166 cd $FOP_BUILD_DIR</userinput></screen> 167 168 </sect3> 169 170 <sect3> 171 <title>Installing FOP required components</title> 177 178 $FOP_BUILD_DIR/JAI.bin && 179 180 cd $FOP_BUILD_DIR && 181 rm JAI.bin</userinput></screen> 182 183 </sect3> 184 185 <sect3> 186 <title>Installing FOP Components</title> 172 187 173 188 <para>Install <application>FOP</application> by running the 174 189 following commands:</para> 175 190 176 <screen><userinput>patch -Np1 -i ../fop-&fop-version;-jdk_1.5.0-1.patch && 177 ./build.sh && 178 sed -i "s/build/lib/" fop.sh</userinput></screen> 191 <screen><userinput>ant && 192 ant javadocs</userinput></screen> 193 194 <para>The unit regression tests were performed in the build step 195 above.</para> 179 196 180 197 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 181 198 182 <screen role="root"><userinput>install -v -d -m755 \ 183 /opt/fop-&fop-version;/{bin,lib,docs/{general,lib,site}} && 184 install -v -m755 fop.sh /opt/fop-&fop-version;/bin && 185 install -v -m644 build/fop.jar lib/avalon-framework-cvs-20020806.jar \ 186 /opt/fop-&fop-version;/lib && 187 install -v -m644 docs/* /opt/fop-&fop-version;/docs && 188 install -v -m644 CHANGES LICENSE README ReleaseNotes.html STATUS \ 189 /opt/fop-&fop-version;/docs/general && 190 install -v -m644 lib/{avalon.LICENSE.txt,readme} \ 191 /opt/fop-&fop-version;/docs/lib && 192 cp -v -R build/site/* /opt/fop-&fop-version;/docs/site && 193 ln -svf fop-&fop-version; /opt/fop</userinput></screen> 194 195 </sect3> 196 197 <sect3> 199 <screen role="root"><userinput>install -v -d -m755 /opt/fop-&fop-version; && 200 cp -v -R * /opt/fop-&fop-version; && 201 ln -v -sf fop-&fop-version; /opt/fop</userinput></screen> 202 203 </sect3> 204 205 <!-- <sect3> 198 206 <title>Installing the Batik JAR</title> 199 207 … … 262 270 <filename class='directory'>/opt/fop-&fop-version;/lib</filename>.</para> 263 271 264 </sect3> 272 </sect3> --> 265 273 266 274 </sect2> … … 272 280 The <application>JAI</application> binary file has a <command>tail</command> 273 281 command imbedded in the file which uses obsolete syntax and causes the 274 file to not unpackcorrectly. This command fixes the obsolete282 file to unpack incorrectly. This command fixes the obsolete 275 283 syntax.</para> 276 284 277 <para><command>$FOP_BUILD_DIR/ ../jai-...-jdk.bin</command>: This285 <para><command>$FOP_BUILD_DIR/JAI.bin</command>: This 278 286 command installs the <application>JAI</application> components 279 287 into the <application>JDK</application> file structure. … … 282 290 <application>FOP</application> source tree.</para> 283 291 284 < para><command>sed -i "s/build/lib/" ...</command>: These commands modify292 <!-- <para><command>sed -i "s/build/lib/" ...</command>: These commands modify 285 293 the installed shell scripts so that the location of the installed 286 <filename>fop.jar</filename> file is correctly identified.</para> 287 288 < para><command>install -v ...; cp -v ...</command>: There is no installation294 <filename>fop.jar</filename> file is correctly identified.</para> --> 295 296 <!-- <para><command>install -v ...; cp -v ...</command>: There is no installation 289 297 script provided by the <application>FOP</application> 290 package. These commands install the package.</para> 291 292 <para><command>ln -svf fop-&fop-version; /opt/fop</command>: This creates a 293 convenience symlink so that <envar>$FOP_HOME</envar> doesn't have to be 294 changed each time there's a package version change.</para> 298 package. These commands install the package.</para> --> 299 300 <para><command>ant</command>: This reads the <filename>build.xml</filename> 301 file and performs the default <option>all</option> target which builds the 302 package and runs the unit regression tests.</para> 303 304 <para><command>ant javadocs</command>: This builds the Java API 305 documentation. Omit this step if desired.</para> 306 307 <para><command>ln -v -sf fop-&fop-version; /opt/fop</command>: This is 308 optional and creates a convenience symlink so that <envar>$FOP_HOME</envar> 309 doesn't have to be changed each time there's a package version change.</para> 295 310 296 311 </sect2> … … 316 331 (including the FO derived from the BLFS XML sources), can lead to memory 317 332 errors. Unless you add a parameter to the <command>java</command> command 318 used in the <command>fop .sh</command> script you may receive messages333 used in the <command>fop</command> script you may receive messages 319 334 similar to the one shown below:</para> 320 335 … … 323 338 324 339 <para>To avoid errors like this, you need to pass an extra parameter to 325 the <command>java</command> command used in the <command>fop .sh</command>340 the <command>java</command> command used in the <command>fop</command> 326 341 script. This can be accomplished by creating a 327 342 <filename>~/.foprc</filename> (which is sourced by the 328 <command>fop .sh</command> script) and adding the parameter to the343 <command>fop</command> script) and adding the parameter to the 329 344 <envar>FOP_OPTS</envar> environment variable.</para> 330 345 331 <para>The <command>fop .sh</command> script looks for a346 <para>The <command>fop</command> script looks for a 332 347 <envar>FOP_HOME</envar> environment variable to locate the 333 348 <application>FOP</application> class libraries. You can create this … … 348 363 <ulink url="http://xml.apache.org/fop/running.html#memory"/>.</para> 349 364 350 <para>To include the <command>fop .sh</command> script in your path,365 <para>To include the <command>fop</command> script in your path, 351 366 update your personal or system-wide profile with the following:</para> 352 367 353 <screen><literal>PATH=$PATH:/opt/fop /bin</literal></screen>368 <screen><literal>PATH=$PATH:/opt/fop</literal></screen> 354 369 355 370 </sect3> … … 366 381 367 382 <seglistitem> 368 <seg>fop .sh and xalan.sh</seg>369 <seg> avalon-framework-cvs-20020806.jar, batik.jar, fop.jar,370 xalan-2.4.1.jar, xercesImpl-2.2.1.jar, and xml-apis.jar. JAI components371 include libmlib_jai.so, jai_codec.jar, jai_core.jar, and383 <seg>fop</seg> 384 <seg>fop.jar and numerous support library classes located in 385 <filename class='directory'>/opt/fop/{build,lib}</filename>; JAI 386 components include libmlib_jai.so, jai_codec.jar, jai_core.jar, and 372 387 mlibwrapper_jai.jar</seg> 373 388 <seg>/opt/fop-&fop-version;</seg> … … 380 395 <?dbhtml list-presentation="table"?> 381 396 382 <varlistentry id="fop .sh">383 <term><command>fop .sh</command></term>397 <varlistentry id="fop-prog"> 398 <term><command>fop</command></term> 384 399 <listitem> 385 400 <para>is a wrapper script to the <command>java</command> command 386 401 which sets up the <application>FOP</application> 387 402 environment and passes the required parameters.</para> 388 <indexterm zone="fop fop .sh">389 <primary sortas="b-fop .sh">fop.sh</primary>403 <indexterm zone="fop fop-prog"> 404 <primary sortas="b-fop">fop</primary> 390 405 </indexterm> 391 406 </listitem>
Note:
See TracChangeset
for help on using the changeset viewer.