The OpenOffice.org 1.0.2 SDK comes with a set of development tools, base libraries and jar files
which can be used to develop Java/C++ components, to embed the OpenOffice.org 1.0.2 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:
- StarOffice 6.0 PP2 or OpenOffice.org 1.0.2 installation
- The SDK works on top of an existing office installation and uses the same libraries as
the office installation.
- JDK (1.3.1_02 or higher)
- A JDK is necessary for developing Java components or applications. An appropriate Java
SDK can be found on
http://java.sun.com/products.
- C++ compiler
- 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:
Solaris, Sun WorkShop 6 update 1 C++ 5.2 2000/09/11
Linux, GNU C++ compiler, gcc version 3.0.1
Windows, Microsoft C++ Compiler, Microsoft Developer Studio 6.0 (cl, version 12.00.8168)
- GNU make (3.79.1 or higher)
- GNU make is used to build the examples of the SDK. GNU make is available from
http://www.gnu.org, it can be ftped via
ftp://ftp.gnu.org/gnu/make
NOTE: Windows user can find an executable of gnu make under
http://www.nextgeneration.dk/gnu/make.zip. It is not recommended to use the Cygwin
make, because it does not work well.
- STLPORT (4.5.3)
- Some examples use the STL. If you want to test this example, you have to install
a version of the STLPORT library on your machine. The STLPORT library is available from
http://www.stlport.org.
The SDK provides a configure script (Unix and WindowsNT/2000/XP) that asks for relevant
directories (SDK, StarOffice, GNU make, Java, C++, STLPORT and ANT). After completing the
configure script a new script will be created (WindowsNT//2000/XP and UNIX) to set the
necessary environment variables for using the SDK and the required tools.
Other versions of the operating system Windows should use the batch program
<OO_SDK_HOME>setsdkenv_windows.bat directly and adopt it to their local environment.
The first time you use the batch program, you must prepare it for your environment.
Edit the script and set the following variables:
OFFICE_HOME |
path to an existing StarOffice or OpenOffice.org installation, e.g.
"/usr/local/StarOffice6.0" |
OO_SDK_HOME |
path to the SDK root directory, e.g. "/usr/local/StarOffice6.0SDK" |
OO_SDK_JAVA_HOME |
path to the JDK |
OO_SDK_CPP_HOME |
path to the C++ compiler (under windows the directory where the
vcvar32.bat file can be found) |
OO_SDK_MAKE_HOME |
path to GNU make |
OO_STLPORT_HOME |
path to the STLPORT installation directory |
SDK_AUTO_DEPLOYMENT |
if this variable is set, the component examples will be automatically
deployed into the Office installation referenced by OFFICE_HOME. See also chapter
"UNO Package installation" from the Developer's Guide.
|
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:
Environment variables for UNIX
Solaris
OFFICE_PROGRAM_PATH |
=$OFFICE_HOME/program
This variable is used to register example components
automatically in your Office installation. If you do not want automatic registration,
please comment this variable out in the script. |
LD_LIBRARY_PATH |
=$OFFICE_PROGRAM_PATH:$OO_SDK_HOME/solsparc/lib:$OO_STLPORT_HOME/lib:
$LD_LIBRARY_PATH
The LD_LIBRARY_PATH will be set or will be extended by the office program path,
the platform dependent lib directory for some additional libraries and the
<OO_STLPORT_HOME>/lib directory (optional).
|
PATH |
=$OO_SDK_HOME/solsparc/bin:$OO_SDK_MAKE_HOME:$OO_SDK_CPP_HOME:$OO_SDK_JAVA_HOME/bin:
$PATH
The PATH variable will be extended by the paths for the SDK development tools,
the compiler, the JDK and GNU make.
|
Linux
OFFICE_PROGRAM_PATH |
=$OFFICE_HOME/program
This variable is used to register example components
automatically in your Office installation. If you do not want automatic registration,
comment this variable out in the script. |
LD_LIBRARY_PATH |
=$OFFICE_PROGRAM_PATH:$SDK_HOM/linux/lib:$OO_STLPORT_HOME/lib:
$LD_LIBRARY_PATH
The LD_LIBRARY_PATH will be set or will be extended by the office program path,
the platform dependent lib directory for some additional libraries and the
<OO_STLPORT_HOME>/lib directory (optional).
|
PATH |
=$OO_SDK_HOME/linux/bin:$OO_SDK_MAKE_HOME:$OO_SDK_CPP_HOME:$OO_SDK_JAVA_HOME/bin:
$PATH
The PATH variable will be extended by the paths for the SDK development tools,
the compiler, the JDK and GNU make.
|
Environment variables for Windows
In addition to setting these environment variables, the script calls the "vcvar32.bat"
batch file, which is provided by the Microsoft Developer Studio to set the necessary
environment variables for the compiler.
OFFICE_PROGRAM_PATH |
=%OFFICE_HOME%\program
This variable is used to register example components
automatically in your Office installation. If you don't want automatic registration,
please comment this variable out in the script. |
PATH |
=%OO_SDK_HOME%\windows\bin;%OO_SDK_MAKE_HOME%;%OO_SDK_CPP_HOME%;%OO_SDK_JAVA_HOME%
\bin;%OFFICE_PROGRAM_PATH%;%OO_STLPORT_HOME%\lib;%PATH%
The PATH variable will be extended by the paths for the SDK development tools,
the compiler, the JDK, the STLPORT library, GNU make and the
<OFFICE_PROGRAM_PATH>.
|
LIB |
=%OO_SDK_HOME%\windows\lib;%OO_STLPORT_HOME\lib;;%LIB%
The LIB variable will be extended by the path to the import libraries which are
necessary for windows.
|
Additionally to setting these environment variables the script calls the
"vcvar32.bat" batch file which is provided by the Microsoft Developer
Studio to set the necessary environment variables for the compiler. |
|