[Open Office] ooo-build on Windows

[David Fraser]

michael meeks wrote:

>Hi David,
>
>On Wed, 2005-10-12 at 13:41 +0200, David Fraser wrote:
>  
>
>>After successfully getting OpenOffice.org building on Windows with the 
>>standard source, I'm trying with ooo-build so that it can handle my 
>>patches etc
>>    
>>
>
>	Nice :-)
>
>  
>
>>I had a few ideas to make this easier, and thought I would bounce them 
>>past here for review (especially since I don't really know autoconf)
>>    
>>
>
>	Sure.
>
>  
>
>>Firstly, it would be nice to autodetect building on Windows... patch 
>>attached to issue a warning if you're using cygwin and don't say 
>>--with-win32
>>    
>>
>
>	Right - it'd of course be nice to warn & just turn on with_win32 or
>whatever - either way; I committed your patch for that: thanks.
>  
>
Thanks

>>Secondly, on Windows you don't want KDE and Gnome support... unless I'm 
>>mistaken. configure seems to assume you do unless you explicitly deny 
>>it. so attached a patch to change this so win32 implies --disable-kde 
>>and --disable-gtk
>>    
>>
>
>	Sure - as it happens they do no harm - and they also do some good: they
>enable the building of the new icon sets / artwork which allow OO.o to
>look (IMHO) rather nicer.
>  
>
OK fine, so on win32 they don't actually try build KDE libraries. that's 
good ;-)

>>I was also wondering, it seems like the --with-ooo-builddir flag allows 
>>you to run on top of an existing tree. Will this cause problems if 
>>you've already been building on that tree or can you just migrate a 
>>standard build into ooo-build using this?
>>    
>>
>
>	I would just move/copy/symlink the build into build/src680-m123 or
>whatever - then it should apply the patches on top of that & do a
>relatively sane incremental build.
>  
>
OK cool I'll give it a go.

>	Great to have you hacking on this too though, it's somewhat under-used
>as you can see :-)
>  
>
This is where the synergy comes in, I need some way of maintaining 
patches and can't bear to do it without ooo-build :-)
Hopefully it'll help

Other things I've noticed:
on HEAD, cairo-1.0.0.tar.gz and glitz-0.4.3.tar.gz aren't getting 
downloaded, but the unpack expects them.
This seems to be because download.in has them in a non-Win32 section. So 
perhaps cairo isn't wanted on Windows...
In this case it would be good to have the default for cairo to be 
disabled on win32
As a result of this, I found that if unpack dies, then it re-unpacks the 
source tarball every time.
This is particularly slow when (like me) you're trying to build on a 
samba drive for lack of space on your Windows machine ;-)
(Incidentally patch also doesn't like renaming readonly files to .orig 
on a shared samba drive)
Still trying to get all the patches to apply, will report more tomorrow...

Cheers
David