Apache OpenOffice (AOO) Bugzilla – Issue 22191
Integrate CLI - UNO language binding into SDK
Last modified: 2004-12-15 12:09:18 UTC
Integrate the CLI - UNO language binding into the OpenOffice.org SDK. That includes: * All new DLLs must be contained in the SDK * Examples must be integrated in SDK * Provide a "How to use" for examples if necessary. * Document requirements for the language binding and building examples
The dlls cli_uno.dll, cli_cppuhelper.dll, cli_types.dll, cli_ure.dll are to be removed from the Office program directory.
odk/docs/examples.html shall contains a link to the Developer's Guide chapter about the CLI-UNO language binding. The Developer's Guide will be updated in a different task. Then we would have to wait until the changes are integrated before we can set the proper link. Or we submit a follow-up task.
When the cws has been integrated then we should contact mh about providing the current SDK on OOo
set target according to pcd task
I submitted the bugtracker bug 114132 which deals with adding a chapter about the CLI - UNO language binding to the developer's guide. When the updated developer's guide is available then the CLI - UNO type mapping document should be removed from udk.openoffice.org. Also, after integrating the cws for this issue the CLI-UNO project page on udk.openoffice.org needs to be revised.
fixed in cws jl2. There is a separate bugtracker bug 114132 which deals with the integration of the documentation into the SDK's developer's guide.
Bugs in master cws prevented me from integrating the cws. We must wait until bugtracker defects 114285, 114240 are fixed and integrated. Also, because of legal complications, the discussion about putting the assemblies in the SDK or office broke out again.
The cws jl2 was resynced to src680 m17. There is a new issue, 114309, which prevents successful testing.
The current solution of distributing the cli assemblies provided that the client has to ship them. That causes legal issues and compatibility issues. Therefore we strive to find a solution to use the Global Assembly Cache with these assemblies.
Since 680m48 the assemblies are installed into the GAC and should also be in the program directory. They are not to be redistributed with the SDK. Now only the examples have to be put into the SDK.
We need to resync to a newer milestone for two reasons: -the examples expect the assemblies to be in the program directory for building. This is only possible when we have abolished the old setup. -A bug in the odk's configureWindows.bat prevents the use of the office installed with native installer, because it contains a space (StarOffice 8)
fixed in cws jl2
verified
SG: checked the SDK: the file settings/dk.mk is referenced from the makefiles of the samples, but the file is missing. So the samples are not usable.
.
SG: checked CLI examples with a correct sdk, everything works fine.
Checked again on src680_m65 and works -> closed.