Apache OpenOffice (AOO) Bugzilla – Issue 30601
Post processing before doing install sets: Windows dlls should get rebased
Last modified: 2004-12-07 08:36:51 UTC
Before the packaging process in instset_native and instsetoo_native can start, we need some preparations for this. -This includes rebase and bind for all dlls and exes on Windows -Calculating the checksums of the files - Adding the checksums into a database (?) For this we need a new cvs module ( "prepare_instset" (?) )
I'll do it differently (checksum handling should be done _after_ successfull testing), but anyway - accepted
RT->JL: You told me about some dlls which must not be rebased. Please list those files here, so that I can explicitly exclude them from possible harmfull operations.
The libraries: cli_types.dll, cli_ure.dll, cli_cppuhelper.dll must not be modified after they have been build. That is, neither rebase nor bind may be called. The reason is, that they contain a hash value which will become invalid when either tool is used. Then they cannot be installed anymore.
I am changing the summary of this issue. The real task is to re-implement a process to rebase windows dlls. Whether its done in a separat module and how this module should be named are just implementation details, I think. Joost did some test measurements for statup performance with and without rebasing. Results Start time in seconds without rebase with rebase Writer 1. Start after reboot 13.9 13.9 10 times average 7.7 7.6 Backing window 1. start after reboot 7.9 6.8 10 times average 3.5 3.4
Obviously there is a fourth dll with must not get rebased: cli_basetypes.dll If you try to rebase one of those mentioned cli_*.dll the rebase tool does not give any error message. Judging from console output and log file (with -l option) everything works well. Nevertheless, it returns error code 227 :-(
I've created a new module postprocess.
A first implementation of rebasing is now active in postprocess/rebase/makefile.mk A more sophisticated mechnism is desirable and should get active before shipping the final release. Follow-up issue for this refinement is i36845
Re-opened to re-assign.
re-assign to QA.
Hi Joost, I implemented rebasing for windows in my CWS 'rebase'. When verifying this issue you should do a crashmail roundtrip in order to check that I did not break the chrashreport tooling.
JA: I measured better startup performance for this cws. CrashReporter roundtrip was OK. Verified on CWS rebase
Adding dependency to issue 20269 (startup performance).
Closing. For follow up work please see issue 36845.