summaryrefslogtreecommitdiff
path: root/odk/docs/install.html
blob: b544ddbdcc053ba273908a9c2bd9b83cca8457cd (plain)
1
<html>
<head>
  <title>[TITLE] - Installation Guide</title>
  <link rel="stylesheet" type="text/css" href="sdk_styles.css">
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <meta name="author" content="J&uuml;rgen Schmidt">
  <meta name="created" content="2004-12-14">
</head>

<body class="sdkbody"><a name="install"/>
<table class="table1" cellpadding=0>
  <tr style="background-image:url(images/sdk_head-2.gif); backgorund-position: bottom; "> 
    <td class="background" colspan="2" align="left"><img src="images/sdk_head-1.gif" width="335" height="109" usemap="#Map" border="0"></td>
    <td class="background" align=right><img src="images/sdk_head-3.gif" width="32" height="109"></td>
  </tr>
  <tr> 
    <td colspan="3"><img  class="nothing10" src="images/nada.gif"></td>
  </tr>
  <tr> 
    <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
    <td> 
      <table class="table2">
	    <tr> 
		  <td colspan="3"><img class="nothing1" src="images/nada.gif"></td>
        </tr>
        <tr> 
          <td> 
          <table class="table3">
		  <tr> 
			<td colspan="2" class="head1">Installation Guide</td>
			<td align="right"><a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a></td>
		  </tr> 
		  </table>
          </td>
        </tr>
		<tr>
          <td> 
          <table class="table3">
		  <tr> 
		  <td colspan="2">
		  <p>The [PRODUCTNAME] SDK comes with a set of development tools, base 
		  libraries, header files and helper class files which can be used to 
		  develop Java/C++ components, to embed the [PRODUCTNAME] application in 
          your own programs, or to use the API (scripting or remote control the 
		  office). For a complete working environment, we have some additional 
		  requirements:</p>
		  </td>
		  </tr> 
		  <tr valign="top"> 
          <td><b>[PRODUCTNAME] installation <em>or</em> URE installation<b></td>
          <td class="content80">The SDK works on top of an existing office 
		  installation and uses the same libraries as the office installation.
          Alternatively, the SDK can be used in combination with a UNO Runtime
          Environment (URE), which comprises only UNO itself, but not the whole
          office application. (Please note that when using a URE, the
          functionality of the SDK is limited; e.g., the various examples in the
          SDK expect an office application and do not work with a plain
          URE.)</td>
          </tr>
		  </tr> 
		  <tr valign="middle"> 
            <td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
          </tr>
		  <tr valign="top"> 
          <td><b>JDK (1.4.1_01 or higher)<b></td>
          <td class="content80">
		  <p>A JDK is necessary for developing Java components or applications. An appropriate Java SDK can be found on <a target="_blank" href="http://java.sun.com/products" title="link to the Java SDK download page (online)">http://java.sun.com/products</a>.</p>
		  <p>If Java 5.0 or higher is used you have to ensure that the used office 
		  installation uses Java 5.0 as well because of class format changes in 
		  Java 5.0. Components build with Java 5.0 cannot be deployed by unopkg 
		  (using the office Java) using a lower Java version than Java 5.0.</p>
		  <p><b>Note</b>: The Java compiler is <b><u>optional</u></b>!</p></td>
          </tr>
		  <tr valign="middle"> 
            <td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
          </tr>
		  <tr valign="top"> 
          <td><b>C++ compiler<b></td>
          <td class="content80">A C++ compiler is necessary for developing C++ 
		  components or applications. UNO depends on a compiler dependent language 
		  binding so that we use the appropriate compiler where a language binding 
		  exists:
		  <table class="table4">
		  <tr>
		  <td class="cell15">Solaris</td>
		  <td class="cell85">Sun WorkShop 6 update 1 C++ 5.2 2000/09/11</td>
		  </tr>
		  <tr>
		  <td class="cell15">Linux</td>
		  <td class="cell80">GNU C++ compiler, gcc version 3.0.1</td>
		  </tr>
		  <tr>
		  <td class="cell15">Windows</td>
		  <td class="cell80">Microsoft C++ Compiler, Microsoft Visual Studio .NET 2003 (cl, version 13.10.3070)</td>
		  </tr>
		  </table>
		  <p><b>Note</b>: The C++ compiler is <b><u>optional</u></b>!</p></td>
          </tr>
		  <tr valign="middle"> 
            <td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
          </tr>
		  <tr valign="top"> 
          <td><b>Microsoft .NET Framework SDK Version 1.0 or higher<b></td>
          <td class="content80">The SDK is required for building CLI applications. 
		  That is, programs written in languages, such as C# or VB.NET.<br>
		  <p><b>Note</b>: The .NET Framework is <b><u>optional</u></b>!</p></td>
          </tr>
		  <tr valign="middle"> 
            <td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
          </tr>
		  <tr valign="top"> 
          <td><b>GNU make (3.79.1 or higher)<b></td>
          <td class="content80">
		  <p>GNU make is used to build the examples of the SDK. GNU make is available from <a target="_blank" href="http://www.gnu.org" title="link to www.gnu.org (online)">http://www.gnu.org</a>, it can be ftped via <a target="_blank" href="ftp://ftp.gnu.org/gnu/make" title="link to gnumake on www.gnu.org (online)">ftp://ftp.gnu.org/gnu/make</a></p>
		  <p><b>Note</b>: Windows user can find an executable of gnu make under <a target="_blank" href="http://www.mingw.org/download.shtml" title="link to the MinGW tools download page (online)">http://www.mingw.org/download.shtml</a>. It is not recommended to use the Cygwin make, because it does not
		  work well. For Solaris you can find gnu make also under <a target="_blank" href="http://www.sunfreeware.com/" title="link to www.sunfreeware.com (online)">http://www.sunfreeware.com/</a>.</td>
          </tr>
		  <tr valign="middle"> 
            <td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
          </tr>
		  <tr valign="top"> 
          <td><b>zip tool (2.3 or higher)<b></td>
          <td class="content80">The zip tool is used to create UNO packages. zip is 
		  a new requirement to make the SDK independent of a Java SDK.<br>
		  If you do not have these already, you can download them from <a target="_blank" href="http://www.info-zip.org" title="link to www.ubfi-zip.org (online)">http://www.info-zip.org</a>. Note: The cygwin zip.exe is not working for the build under 
		  the 4NT shell. You have to use the native w32 version.</td>
          </tr>
		  <tr valign="middle"> 
            <td colspan="2"><img class="line" src="images/sdk_line-2.gif"></td>
          </tr>
		  <tr> 
		    <td><img class="nothing10" src="images/nada.gif"></td>
			<td align="right">
			<a href="#install" title="link to the top of this page"><img class="navigate" src="images/nav_up.png"></a>
			<a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a></td>
		  </tr>
		  <tr valign="middle"> 
          <td colspan="2">
		  <p>The SDK provides a configure script (Unix and Windows2000/XP) that 
		  asks for relevant directories (SDK, StarOffice, GNU make, Java, C++). 
		  After completing the configure script a new script will be created 
		  (Windows2000/XP and UNIX) to set the necessary environment variables for 
		  using the SDK and the required tools. Under UNIX the configure script 
		  uses Perl. LINUX systems should have installed a working perl version and 
		  for Solaris you can find a working Perl version under <a target="_blank" href="http://www.sunfreeware.com/" title="link to www.sunfreeware.com (online)">http://www.sunfreeware.com/</a> if necessary. Under Windows the configure script uses 
		  Windows Script and a JScipt. If you have problems with Windows Script you 
		  can either use the <b>&lt;OO_SDK_HOME&gt;\setsdkenv_windows.bat</b> 
		  directly or you can download a newer version of <a href ="http://www.microsoft.com/downloads/details.aspx?FamilyId=C717D943-7E4B-4622-86EB-95A22B832CAA&displaylang=en" link"link to the download page for the Windows Script">Windows Script</a>.
          </p>
		  <ul>
		    <li><b>configure</b>&nbsp;&nbsp;-> for Unix
            <li><b>configureWindows.bat</b></a>&nbsp;&nbsp;-> for Windows2000/XP 
			or newer versions
          </ul>
          <p>Other versions of the operating system Windows should use the batch 
		  program <b>&lt;OO_SDK_HOME&gt;\setsdkenv_windows.bat</b> directly and 
		  adopt it to their local environment.</p>
		  <p>The first time you use the batch file, you must prepare it for your 
		  environment. Edit the script and set the following variables:</p>
		  <table class="table4">
		  <tr valign="top">
		  <td class="cell20"><b>OFFICE_HOME</b></td>
		  <td class="cell80">path to an existing StarOffice&#153 or OpenOffice.org 
		  base installation, e.g. &quot;/opt/staroffice8&quot;. Please take care 
		  that it is not a user installation only. Exactly one of OFFICE_HOME
          and OO_SDK_URE_HOME must be set (the other should be either unset or
          set to an empty value).</td>
		  </tr>
          <tr>
          <td class="cell20"><b>OO_SDK_URE_HOME</b></td>
          <td class="cell80">path to an existing UNO Runtime Environment
          installation, e.g. &quot;/opt/openoffice.org/ure&quot;. Exactly one of
          OFFICE_HOME and OO_SDK_URE_HOME must be set (the other should be
          either unset or set to an empty value).</td>
          </tr>
		  <tr>
		  <td class="cell20"><b>OO_SDK_HOME</b></td>
		  <td class="cell80">path to the SDK root directory, e.g. 
		  &quot;/usr/local/StarOffice8_SDK&quot;</td>
		  </tr>
		  <tr>
		  <td class="cell20"><b>OO_SDK_JAVA_HOME</b></td>
		  <td class="cell80">path to a JDK root directory. The JDK is 
		  <b>optional</b> and only necessary if you like to run the Java examples 
		  or if you like to use the SDK environment to develop your own Java 
		  solution.</td>
		  </tr>
		  <tr>
		  <td class="cell20"><b>OO_SDK_CPP_HOME</b></td>
		  <td class="cell80">path to the C++ compiler (under windows the directory 
		  where the &quot;<i>vcvar32.bat</i>&quot; file can be found). The C++ 
		  compiler is <b>optional</b> and only necessary for building the C++ 
		  examples.</td>
		  </tr>
		  <tr>
		  <td class="cell20"><b>OO_SDK_CLI_HOME</b></td>
		  <td class="cell80">path to the C# compiler and VB.NET compiler (under 
		  windows this directory can be found under the system directory (e.g. 
		  c:\WINXP\Microsoft.NET\Framework\v1.0.3705). The compilers are 
		  <b>optional</b> and only necessary for building the CLI examples.<br>
		  <b>Note: Windows only!</b></td>
		  </tr>
		  <tr>
		  <td class="cell20"><b>OO_SDK_MAKE_HOME</b></td>
		  <td class="cell80">path to GNU make.</td>
		  </tr>
		  <tr>
		  <td class="cell20"><b>OO_SDK_ZIP_HOME</b></td>
		  <td class="cell80">path to the 'zip' tool.</td>
		  </tr>
		  <tr>
		  <td class="cell20"><b>OO_SDK_OUTPUT_DIR</b></td>
		  <td class="cell80">path to an existing directory where the example output 
		  is generated. The output directory is <b>optional</b>, default is that 
		  the output is generated in the SDK directory itself. If an output 
		  directory is specified, the output is generated in a SDK dependent 
		  subdirectory in this directory (e.g. &lt;OO_SDK_OUTPUT_DIR&gt;
		  /[PRODUCTNAME]/LINUXExample.out)</td>
		  </tr>
		  <tr>
		  <td class="cell20"><b>SDK_AUTO_DEPLOYMENT</b></td>
		  <td class="cell80">if this variable is set, the component examples will 
		  be automatically deployed into the Office installation referenced by 
		  OFFICE_HOME. See also chapter <a href="DevelopersGuide/Components/Components.xhtml#1_9_1_UNO_Package_Installation_Using_unopkg" title="link to &quot;UNO Package Installation Using unopkg&quot; chapter in the Developer's Guide">&quot;UNO Package Installation Using unopkg&quot;</a> from the Developer's Guide.
          This variable is only relevant when OFFICE_HOME is set.</td>
		  </tr>
		  </table>
		  <p>You have to run the <b>setsdkenv_XXX</b> script every time you want to 
		  use the configured SDK environment. The settings are local for the current
		  shell under Windows or the new started shell under UNIX. Under UNIX you 
		  have now also the possibility to source one of the prepared environment 
		  script files (&quot;setsdkenv_unix.sh&quot; or 
		  &quot;setsdkenv_unix.csh&quot; dependent of your used shell) to prepare 
		  your current shell instead of starting a new shell.</p>
		  </td>
          </tr>
		  <tr valign="middle"> 
            <td colspan="2"><img class="line" src="images/sdk_line-2.gif"></td>
          </tr>
		  <tr> 
		    <td><img class="nothing10" src="images/nada.gif"></td>
			<td align="right">
			<a href="#install" title="link to the top of this page"><img class="navigate" src="images/nav_up.png"></a>
			<a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a></td>
		  </tr>
		  <tr>
		  <td colspan="2">
		  <p class="head2">Manual Setting</p>
		  <p>If you do not want to use the script to set your working 
		  environment, you must set the appropriate environment variables by 
		  yourself. The script sets the following environment variables.</p>
		  <p class="head3">Common Environment Variables</p>
		  <table class="table4">
          <tr valign="top">
          <td class="cell20">OO_SDK_URE_BIN_DIR</td>
          <td class="cell80">The path within the chosen office or URE
          installation where binary executables are located (e.g.,
          <i>$OFFICE_HOME/program</i> for an office installation, or
          <i>$OO_SDK_URE_HOME/bin</i> for a Unix URE installation).</td>
          </tr>
          <tr valign="top">
          <td class="cell20">OO_SDK_URE_LIB_DIR</td>
          <td class="cell80">The path within the chosen office or URE
          installation where dynamic libraries are located (e.g.,
          <i>$OFFICE_HOME/program</i> for an office installation, or
          <i>$OO_SDK_URE_HOME/lib</i> for a Unix URE installation).</td>
          </tr>
          <tr valign="top">
          <td class="cell20">OO_SDK_URE_JAVA_DIR</td>
          <td class="cell80">The path within the chosen office or URE
          installation where Java JARs are located (e.g.,
          <i>$OFFICE_HOME/program/classes</i> for an office installation, or
          <i>$OO_SDK_URE_HOME/share/java</i> for a Unix URE installation).</td>
          </tr>
		  <tr valign="top">
		  <td class="cell20">CLASSPATH</td>
		  <td class="cell80">
          =<i>$OO_SDK_URE_JAVA_DIR/juh.jar;
              $OO_SDK_URE_JAVA_DIR/jurt.jar;
              $OO_SDK_URE_JAVA_DIR/ridl.jar;
              $OO_SDK_URE_JAVA_DIR/unoloader.jar;
              [$OO_SDK_URE_JAVA_DIR/unoil.jar;]
              $CLASSPATH</i><br>
          <p>The classpath will be set or extended to the necessary jar files of 
		  the specified office installation. (<i>unoil.jar</i> is only included
          when OFFICE_HOME is set.)</p>
		  </td>
		  </tr>
		  <tr valign="top">
		  <td class="cell20">OFFICE_PROGRAM_PATH</td>
		  <td class="cell80">=<i>$OFFICE_HOME/program</i><br>
		  <p>This variable is used to find for example the office type library and 
		  the UNO package deployment tool. This variable is only relevant when
          OFFICE_HOME is set.</p>
		  </td>
		  </tr>
		  <tr valign="top">
		  <td class="cell20">UNO_PATH</td>
		  <td class="cell80">=<i>$OFFICE_PROGRAM_PATH</i><br>
          <p>This variable is used to ensure that the new C++ UNO bootstrap 
		  mechanism uses the configured office installation of the SDK. Normally 
		  does the bootstrap mechanism find the default office installation for the
		  user on the system. This variable is optional but is set from the scripts
		  to ensure a homogeneous environment. Especially useful during development
		  where you have maybe more than one office installation installed. This
          variable is only relevant when OFFICE_HOME is set.</p>
		  </td>
		  </tr>
		  </table>
		  <p class="head3">Environment Variables for UNIX</p>
		  <p class="head4">Solaris</p>
		  <table class="table4">
		  <tr valign="top">
		  <td class="cell20">LD_LIBRARY_PATH</td>
		  <td class="cell80">=<i>$OO_SDK_URE_LIB_DIR: $OO_SDK_HOME/(solsparc|solintel)/lib: $LD_LIBRARY_PATH</i><br>
		  <p>The LD_LIBRARY_PATH will be set or will be extended by the office/URE
		  library path, the platform dependent lib directory for some additional 
		  libraries.</p>
		  </td>
		  </tr>
		  <tr valign="top">
		  <td class="cell20">PATH</td>
		  <td class="cell80">=<i>$OO_SDK_HOME/(solsparc|solintel)/bin:$OO_SDK_MAKE_HOME: $OO_SDK_ZIP_HOME: [$OO_SDK_CPP_HOME:] [$OO_SDK_JAVA_HOME/bin:] $OO_SDK_URE_BIN_DIR: $PATH</i></b><br>
          <p>The PATH variable will be extended by the paths for the SDK development
		  tools, the compiler, the JDK, GNU make, the zip tool and the 
		  OO_SDK_URE_BIN_DIR (where the compiler or the JDK are 
		  optional).</p>
		  </td>
		  </tr>
          <tr>
          <td colspan="2" class="cell80">When OO_SDK_URE_HOME is set, the script
          additionally creates symbolic links to the public dynamic libraries of
          the URE in <i>$OO_SDK_HOME/(solsparc|solintel)/lib</i> (which are
          needed for linking).</td>
          </tr>
		  </table>
		  <p class="head4">Linux</p>
		  <table class="table4">
		  <tr valign="top">
		  <td class="cell20">LD_LIBRARY_PATH</td>
		  <td class="cell80">=<i>$OO_SDK_URE_LIB_DIR: $SDK_HOME/linux/lib: $LD_LIBRARY_PATH</i><br>
		  <p>The LD_LIBRARY_PATH will be set or will be extended by the office/URE
		  library path, the platform dependent lib directory for some additional 
		  libraries.</p>
		  </td>
		  </tr>
		  <tr valign="top">
		  <td class="cell20">PATH</td>
		  <td class="cell80">=<i>$OO_SDK_HOME/linux/bin:$OO_SDK_MAKE_HOME: $OO_SDK_ZIP_HOME: [$OO_SDK_CPP_HOME:] [$OO_SDK_JAVA_HOME/bin:] $OO_SDK_URE_BIN_DIR: $PATH</i><br>
		  <p>The PATH variable will be extended by the paths for the SDK development
		  tools, the compiler, the JDK, GNU make, the zip tool and the 
		  OO_SDK_URE_BIN_DIR (where the compiler and the JDK are 
		  optional).</p>
		  </td>
		  </tr>
          <tr>
          <td colspan="2" class="cell80">When OO_SDK_URE_HOME is set, the script
          additionally creates symbolic links to the public dynamic libraries of
          the URE in <i>$OO_SDK_HOME/linux/lib</i> (which are needed for
          linking).</td>
          </tr>
		  </table>
		  <p class="head3">Environment Variables for Windows</p>
		  <table class="table4">
		  <tr valign="top">
		  <td class="cell20">PATH</td>
		  <td class="cell80">=<i>%OO_SDK_HOME%\windows\bin; %OO_SDK_MAKE_HOME%; %OO_SDK_ZIP_HOME%; [%OO_SDK_CLI_HOME%;] [%OO_SDK_CPP_HOME%;] [%OO_SDK_JAVA_HOME%\bin;] %OO_SDK_URE_BIN_DIR%; %PATH%</i><br>
		  <p>The PATH variable will be extended by the paths for the SDK development
		  tools, the compiler, the JDK, GNU make, the zip tool and the 
		  OO_SDK_URE_BIN_DIR.</p>
		  </td>
		  </tr>
		  <tr valign="top">
		  <td class="cell20">LIB</td>
		  <td class="cell80">=<i>%OO_SDK_HOME%\windows\lib; %LIB%</i><br>
		  <p>The LIB variable will be extended by the path to the import libraries 
		  which are necessary for windows.</p>
		  </td>
		  </tr>
		  <tr valign="top">
		  <td colspan="2" class="cell80">Additionally to setting these environment 
		  variables the script calls the &quot;<i>vcvar32.bat</i>&quot; batch file 
		  which is provided by the Microsoft Developer Studio to set the necessary 
		  environment variables for the compiler.</td>
		  </tr>
		  </table>
		  </td>
		  </tr>
		  </table>
          </td> 
		</tr>
	  </table>
	</td>  	
  </tr>
  <tr> 
    <td colspan="3"><img class="nothing30" src="images/nada.gif"></td>
  </tr>
  <tr> 
    <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
  </tr>
  <tr> 
    <td colspan="3"> 
      <div align="center"><p>Copyright 2005 Sun Microsystems, Inc.</p></div>
    </td>
  </tr>
</table>
<map name="Map">
  <area shape="rect" coords="10,68,93,105" href="http://www.sun.com">
</map>
</body>
</html>