| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
| <HTML> |
| <head> |
| <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1251"> |
| <TITLE>External Components</TITLE> |
| <META NAME="GENERATOR" CONTENT="OpenOffice.org 1.1 (Win32)"> |
| <META NAME="CREATED" CONTENT="20030522;19110663"> |
| <META NAME="CHANGED" CONTENT="20030523;14215217"> |
| </head> |
| <body LANG="en-US" DIR="LTR"> |
| <h1>External Components</h1> |
| <P>There are several external components which are used to build the |
| office suite. Most of the external components are in the source tree, |
| so you do not have to download them separately. For further external |
| download information, see the appropriate build guide for your platform |
| referenced from the <a HREF="index.html">main tools page</a>. |
| </P> |
| <p>It is possible to build using the system versions of the external modules |
| Please see <code>configure --help</code> for the options to use the system |
| versions. This is especially valuable to packagers of Openoffice.org.</p> |
| <P>Most of these external components are gzipped tarballs. These |
| external tarballs are in the <CODE><name>/download</CODE> directory |
| under the source tree top-level directory. Some are stored in the external |
| directory under <code>external/download</code> because they have not migrated |
| to this new directory structure. |
| </P> |
| <P>These modules are built throughout the build process. |
| Early in the build process it will also process build the |
| <CODE>external</CODE> module. The process extracts the tarballs. In |
| some cases it patches with specific OpenOffice.org patches. It then compiles |
| the components. The deliver program then copies the |
| components into the <CODE>solver</CODE> tree. |
| </P> |
| <P>If the correct external components are not present in your source |
| tree, the build will not work. Some of these external components are |
| platform-dependent. That is, you do not need all of them if you are |
| not building on that particular platform. If the required components |
| are present, the build process writes a text file called <CODE>patchinf</CODE> |
| to the <CODE>external/</CODE><VAR>component-name</VAR> directory. If |
| the required components are not present, the build process writes a |
| text file called <CODE>patcherror</CODE> to the |
| <CODE>external/</CODE><VAR>component-name</VAR> directory. The |
| <CODE>patcherror</CODE> file specifies what components are missing, |
| and where they are missing from. |
| </P> |
| <P>In some instances the original tarballs have been minimized to |
| include only the relevant files. These tarballs have been renamed |
| with a <CODE>-stub</CODE> suffix. The stub tarball version is an |
| attempt to save space and reduce the download time. If you want to |
| use the original tarballs, you must modify the appropriate patch |
| script in the <CODE>external/</CODE><VAR>component-name</VAR> |
| directory. |
| </P> |
| <P><B>ADO</B></P> |
| <P>Platform: Win32</P> |
| <P>Version: Microsoft Platforms SDK, April 2000 Edition</P> |
| <P>URL: |
| <A HREF="http://www.microsoft.com/msdownload/platformsdk/setuplauncer.htm">http://www.microsoft.com/msdownload/platformsdk/setuplauncer.htm</A></P> |
| <P>Notes: Download the Platform SDK Setup, <CODE>psdk-86.exe</CODE>, |
| from the Custom Installation section. Then run it in your Win32 |
| environment. This starts an interactive download program. <BR>Follow |
| the instructions on the screen. At the Custom Installation screen, |
| select Build Environment/Data Access Service/OLE DB from the Custom |
| Installation tree. This downloads a number of files to your Win32 |
| environment. You only need to copy the header file <CODE>adoctint.h</CODE> |
| to the <CODE>external/download</CODE> directory under the source tree |
| top-level directory. |
| </P> |
| <P><B>Network Audio System (audio)</B></P> |
| <P>Platform: Linux, Solaris</P> |
| <P>Version: 1.6</P> |
| <P>URL: <A HREF="http://www.radscan.com/nas.html">http://www.radscan.com/nas.html</A></P> |
| <P><B>Dmake - Build Environment Tool</B></P> |
| <P>Platform: All</P> |
| <P>Version: 3.2.1</P> |
| <P>URL: <A HREF="http://www.wticorp.com/projects/dmake">http://www.wticorp.com/projects/dmake</A></P> |
| <p>This link is dead. OpenOffice.org has taken over this project.</p> |
| <P><B>XML Parser Toolkit (expat)</B></P> |
| <P>Platform: All</P> |
| <P>Version: 1.2</P> |
| <P>URL: <A HREF="ftp://ftp.jclark.com/pub/xml/expat.zip">ftp://ftp.jclark.com/pub/xml/expat.zip</A></P> |
| <P>Notes: For more information, see |
| <A HREF="http://www.jclark.com/xml/expat.html">http://www.jclark.com/xml/expat.html</A>.</P> |
| <P><B>Glibc - command line parsing<</B></P> |
| <P>Platform: All</P> |
| <P>Version: 2.1.3</P> |
| <P>URL: <A HREF="ftp://ftp.gnu.org/gnu/glibc/glibc-2.1.3.tar.gz">ftp://ftp.gnu.org/gnu/glibc/glibc-2.1.3.tar.gz</A></P> |
| <P>Notes: For more information, see <A HREF="http://www.gnu.org/">http://www.gnu.org</A>. Stub stored in internal.</P> |
| <P><B>JPEG Image Compression</B></P> |
| <P>Platform: All</P> |
| <P>Version: 6b</P> |
| <P>URL: <A HREF="ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz">ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz</A></P> |
| <P>Notes: For more information, see <A HREF="http://www.ihg.org/">http://www.ijg.org</A>.</P> |
| <P><B>NP_SDK</B></P> |
| <P>Platform: All</P> |
| <P>Version: Mozilla Milestone 16</P> |
| <P>URL: |
| <A HREF="http://www.mozilla.org/projects/seamonkey/release-notes/index.html">http://www.mozilla.org/projects/seamonkey/release-notes/index.html</A></P> |
| <P>Notes: You must get the M16 tarball.</P> |
| <P><B>ODBC</B></P> |
| <P>Platform: Win32</P> |
| <P>Version: 3.0</P> |
| <P>URL: |
| <A HREF="http://www.microsoft.com/msdownload/platformsdk/setuplauncer.htm">http://www.microsoft.com/msdownload/platformsdk/setuplauncer.htm</A></P> |
| <P>Notes: Download the Platform SDK Setup, <CODE>psdk-86.exe</CODE>, |
| from the Custom Installation section. Then run it in your Win32 |
| environment. This starts an interactive download program. <BR>Follow |
| the instructions on the screen. At the Custom Installation screen, |
| select Build Environment/Data Access Service/OLE DB from the Custom |
| Installation tree. This downloads a number of files to your Win32 |
| environment. You only need to copy the header file <CODE>SqlUcode.h</CODE> |
| to the <CODE>external/download</CODE> directory under the source tree |
| top-level directory. |
| </P> |
| <P><B>PGP</B></P> |
| <P>Platform: Win32</P> |
| <P>Version: 5.5, 6.0, and 6.5</P> |
| <P>URL: |
| <BR><A HREF="http://www.pgpi.org/products/pgp/versions/freeware/win32/5.5.3i/"> |
| http://www.pgpi.org/products/pgp/versions/freeware/win32/5.5.3i</A><BR> |
| <A HREF="http://www.pgpi.org/products/pgp/versions/freeware/win32/6.0.2i/"> |
| http://www.pgpi.org/products/pgp/versions/freeware/win32/6.0.2i</A><BR> |
| <A HREF="http://www.pgpi.org/products/pgp/versions/freeware/win32/6.5.1i/"> |
| http://www.pgpi.org/products/pgp/versions/freeware/win32/6.5.1i</A> |
| </P> |
| <P>Notes: You must download the soure tarballs for all three versions |
| of PGP.</P> |
| <P><B>Sane</B></P> |
| <P>Platform: All</P> |
| <P>Version: 1.0</P> |
| <P>URL: <A HREF="http://www.mostang.com/sane/source.html">http://www.mostang.com/sane/source.html</A> |
| </P> |
| <P>Notes: Get the <CODE>sane-1.00.tar.gz</CODE> file.</P> |
| <P><B>STLPort - C++ Standard Template Library (Std2)</B></P> |
| <P>Platform: All</P> |
| <P>Version: 4.0 4.5 & 4.5.3</P> |
| <P>URL: <A HREF="http://www.stlport.org/download.shtml">http://www.stlport.org/download.shtml</A> |
| </P> |
| <P>Notes: For more information, see <A HREF="http://www.stlport.org/">http://www.stlport.org</A></P> |
| <P><B>Twain</B></P> |
| <P>Platform: All</P> |
| <P>Version: 1.9</P> |
| <P>URL: <A HREF="http://www.twain.org/devfiles/twain.h">http://www.twain.org/devfiles/twain.h</A> |
| </P> |
| <P>Notes: You only need to download the <CODE>twain.h</CODE> header |
| file.</P> |
| <P><B>Zlib Compression Library</B></P> |
| <P>Platform: All</P> |
| <P>Version: 1.1.3</P> |
| <P>URL: <A HREF="ftp://ftp.uu.net/pub/archiving/zip/zlib/zlib.tar.gz">ftp://ftp.uu.net/pub/archiving/zip/zlib/zlib.tar.gz</A> |
| </P> |
| <P>Notes: For more information, see |
| <A HREF="http://www.info-zip.org/pub/infozip/zlib/">http://www.info-zip.org/pub/infozip/zlib</A>.</P> |
| <P><B>Neon</B></P> |
| <P>Platform: All</P> |
| <P>Version: 0.23.5</P> |
| <P>URL: <A HREF="http://www.webdav.org/neon/">http://www.webdav.org/neon</A> |
| </P> |
| <P><B>PATCH (GNU)</B></P> |
| <P>Platform: Solaris</P> |
| <P>Version: 2.5.4</P> |
| <P>URL: <A HREF="http://ftp.gnu.org/pub/gnu/patch/patch-2.5.4.tar.gz">http://ftp.gnu.org/pub/gnu/patch/patch-2.5.4.tar.gz</A></P> |
| <P>Notes: There is patch program in Solaris system. Make sure that in |
| your build environment the GNU patch is used (Just run “patch |
| -v” to prove it).</P> |
| <a name="gperf"></a><P><B>gperf (GNU)</B> |
| </P> |
| <P>Platform: All</P> |
| <P>Version: 3.0.3</P> |
| <P>URL Linux: <A HREF="ftp://ftp.gnu.org/pub/gnu/gperf/gperf-3.0.3.tar.gz">ftp://ftp.gnu.org/pub/gnu/gperf/gperf-3.0.3.tar.gz</A></P> |
| <p>URL Windows: <A HREF="http://gnuwin32.sourceforge.net/packages/gperf.htm">http://gnuwin32.sourceforge.net/packages/gperf.htm</A></p> |
| <p>URL Solaris: <A HREF="ftp://gd.tuwien.ac.at/platform/sun/solaris/freeware/intel/10/gperf-3.0.3-sol10-x86-local.gz">ftp://gd.tuwien.ac.at/platform/sun/solaris/freeware/intel/10/gperf-3.0.3-sol10-x86-local.gz</A></p> |
| <P>Notes: For more information see <a href="http://www.gnu.org/software/gperf/gperf.html">http://www.gnu.org/software/gperf/gperf.html</a>.</P> |
| </body> |
| </HTML> |