The ODK includes the binaries of the base libraries, C++ header files, all OpenOffice idl-files, .jar-files and development tools (code generators, tools to register components, etc.). The ODK additionally includes some source examples and makefiles, that only require gnumake + C++-compiler or java compiler. The makefiles can be used as a template to integrate the development kit into any build environment.
The development kit is provided in future for every OpenOffice build.
In general, a tarball containing the documentation and a tarball/zipfile for each supported platform containing the binaries can be downloaded.
odk3.0.0 Description | +classes contains all necessary class files for java UNO | +examples | +cpp contains C++ examples, see README in each directory for build instructions +java Java examples, see README build instructions | + idl contains all interface decriptions used in OpenOffice | + include C / C++ includefiles for the base libraries | + settings Contains GNU makefiles, which are included by the example-Makefiles | + windows (+ solsparc) (+ linux) | +bin Contains UNO tools, registry and on windows dlls +lib Contains on unix the shared libraries and on windows import libraries | + www Contains the whole ODK documentation
In general you use the import libraries and headers from the ODK to develop your C++ components ( see the examples for sample makefiles). You can then take the resulting shared library and put it into the openoffice-installpath/program directory. Use the regcomp tool to register your component. You can then start OpenOffice and instantiate your component e.g. via basic.
Note that you can then deliver the shared library to other users, which only have an OpenOffice installed. As soon as ODK has frozen the API, you can put your once built binary under every new version of the OpenOffice.
- FAQ
- Tools documentation
- Guide to language independent UNO
The documentation can also be accessed online via http://udk.openoffice.org and http://api.openoffice.org. Please note, that in early revisions of the ODK, the documentation may not be available as a separate tarball due to build problems, you can alternatively check out the documentation :
cvs -d :pserver:anoncvs@anoncvs.openoffice.org:/cvs login Password: anoncvs cvs -d :pserver:anoncvs@anoncvs.openoffice.org:/cvs -z3 co oo/udk/www cvs -d :pserver:anoncvs@anoncvs.openoffice.org:/cvs -z3 co oo/api/www