[Open Office] Windows build cycle

[Tor Lillqvist]

to 2006-09-21 klockan 20:16 +0200 skrev Robert Vojta:

> Please, anyone who is building OpenOffice.org for Windows, can you
> send me your tip & tricks & hacks for cycle speed-up?

Well, one trick is to use Filesys::CygwinPaths::win32path in the Perl
modules that build the installer instead of spawning cygpath -w
thousands of times. This speeds up the work in instsetoo_native
significantly. See
http://www.openoffice.org/issues/show_bug.cgi?id=69671 . 

But that is just the instsetoo_native phase. (And when hacking on OO.o
code, you don't want to build the installer after each change, of
course. Just copy the fresh DLLs with code you have hacked on into the
installation location on your machine... If you want to debug, build
with debug=true, and copy the corresponding .pdb files, too.)

As for speeding up the actual compilation of OO.o, I assume using
Volker's guw.exe patch will help quite a bit. (Using an executable
guw.exe instead of the guw.pl script.) I haven't tried that myself, but
it is available in a CWS whose name I can't recall now. (Why can't the
EIS web UI offer to show the diffs between the reference milestone and a
CWS btw?)

Then there is other work going on to speed up the build which will take
some time before it is generally usable and available. Check KaiB's talk
from OOoCon.

--tml