[tools-dev] OOo source split

2007-10-08 Thread Jan Holesovsky
Hi,

During the OOoCon, Petr had a presentation about the OOo package splitting.  
The most important part for a (Linux) package maintainer was to be able to 
build parts of OpenOffice.org separately; the thing is that with all the 
localizations, we are unable to get the build times under some 7 hours.  But 
the build could be done nicely in parallel (on the level of machines, not 
processors) if the sources were split correctly, with correct rpms and -devel 
rpms [of course, applies to debs as well ;-)].  And of course, the -noarch 
parts like the translations could be built just once for all architectures.

I propose the following split of the sources [the sizes are of the unpacked 
sources]:

75M ure
25M ooo-bootstrap
141Mooo-libs-core
101Mooo-libs-guitoolkit
142Mooo-libs-3rdparty
17M ooo-apps-base
28M ooo-apps-calc
38M ooo-apps-extensions
14M ooo-apps-chart
40M ooo-apps-impress
40M ooo-apps-writer
59M ooo-artwork
107Mooo-filters
888Mooo-l10n
48M ooo-sdk
72M ooo-testing
(1.8G   total)

(See below the content of these tarballs/archives).  I don't want the 
granularity to be too fine (we would get the modules we have now, but as 
separate packages), and OTOH the current 5 packages are too few.  The build 
order of these would be:

ooo-bootstrap
ooo-libs-3rdparty
ure
ooo-libs-guitoolkit
ooo-libs-core
[the rest in whatever sequence/in parallel]

This would tremendously decrease the learning curve for the new developers as 
well.  Imagine someone who wants to start hacking on Calc.  Instead of the 
monster 1.8G sources, he would have to handle 512MB.  Additionally, the goal 
of the modern Linux distros should be to get rid of the ooo-libs-3rdparty 
completely - it contains just stuff that is available from other sources 
anyway [-system stuff], and the distros have packages for them -, thus 
additional 142M down, doing it just 370M.  And that is much more pleasant, 
isn't it? ;-)

Of course, this is not finalized etc. - that's why I'm asking for comments.  
So far I was able to build in this order with few hacks, eg. scp2 should be 
split so that the file lists are local, the l10n part must be buildable 
separtately, etc.

So - what do you think? ;-)  ooo-l10n in the current proposal contains (in 
addition to the few modules) all the localize.sdf's - should we split this a 
bit as well?

Following is the proposal what I think belongs where:

= ure =

bridges
cli_ure
codemaker
cppu
cppuhelper
cpputools
idlc
io
javaunohelper
jurt
jut
jvmaccess
jvmfwk
offapi
offuh
pyuno
rdbmaker
registry
remotebridges
ridljar
sal
salhelper
stoc
store
udkapi
unoil
ure
xml2cmp

= ooo-apps-base =

dbaccess
reportdesign

= ooo-apps-calc =

sc

= ooo-apps-extensions =

accessibility
automation
basctl
bean
crashrep
embedserv
extensions
forms
javainstaller2
lingucomponent
MathMLDTD
package
setup_native
UnoControls
wizards
xmlsecurity

= ooo-apps-chart =

chart2

= ooo-apps-impress =

animations
sd
slideshow

= ooo-apps-writer =

starmath
sw

= ooo-artwork =

default_images
external_images
ooo_custom_images

= ooo-bootstrap =

config_office
dmake
instsetoo_native
postprocess
scp2
solenv
soltools
stlport

= ooo-filters =

binfilter
filter
hwpfilter
unoxml
writerfilter
writerperfect
xmerge

= ooo-libs-core =

avmedia
basic
configmgr
connectivity
desktop
embeddedobj
eventattacher
fileaccess
fpicker
framework
idl
linguistic
officecfg
oovbaapi
sandbox
scripting
sfx2
shell
sj2
so3
svx
sysui
ucb
uui
xmlhelp
xmloff
xmlscript
XmlSearch

= ooo-libs-guitoolkit =

basebmp
basegfx
canvas
comphelper
cppcanvas
dtrans
goodies
i18npool
i18nutil
o3tl
padmin
psprint
psprint_config
regexp
rsc
sax
scaddins
sot
svtools
toolkit
tools
transex3
ucbhelper
unotools
vcl
vos

= ooo-libs-3rdparty =

afms
agg
beanshell
berkeleydb
bitstream_vera_fonts
boost
curl
dictionaries
epm
expat
external
fondu
freetype
hsqldb
icu
jfreereport
jpeg
libegg
libtextcat
libwpd
libxml2
libxmlsec
libxslt
moz
msfontextract
nas
neon
np_sdk
portaudio
python
rhino
sane
sndfile
twain
unixODBC
vigra
xalan
xt
x11_extensions
zlib

= ooo-l10n =

extras
helpcontent2
readlicense_oo

= ooo-sdk =

autodoc
cosv
odk
sdk_oo
udm
unodevtools

= ooo-testing =

qadevOOo
smoketestoo_native
testshl2
testtools

Regards,
Jan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[tools-dev] Re: [porting-dev] cygwin build problem on sb71

2007-10-08 Thread Volker Quetschke
Hi Stephan,

first, please use [EMAIL PROTECTED], W32-bash is not really a port, but
the only supported way to build OOo on windows outside of Hamburg ;)

Stephan Bergmann wrote:
 Hi all,
 
 I received a mail that an apparently cygwin-based buildbot build of CWS
 sb71 failed, with linker errors like
 
   LINK : fatal error LNK1181: cannot open input file
 ´C:\cygwin\DELAYLOAD;sal3.dll´
 
 This is obviously due to solenv/inc/libs.mk:1.113.8.9 l. 354
 
   SALLIB=isal.lib /DELAYLOAD:sal$(UDK_MAJOR).dll

Yeah, looks like guw thought /DELAYLOAD is a path. This would not
happen if you use - instead of /, so try -DELAYLOAD:sal$(UDK_MAJOR).dll
instead.

(If that should fail for some reason we have to add a special clause
to config_office/guw/guw.cc to make it ignore that switch.)

 
 which apparently is used for both standard Windows builds and
 cygwin-based ones.

See my comment about standard Windows builds above :)


  Volker

 
 Any suggestions how best to fix that?
 
 Thanks,
 -Stephan
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 


-- 
= http://wiki.services.openoffice.org/wiki/Debug_Build_Problems  =
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D



signature.asc
Description: OpenPGP digital signature


[tools-dev] Is someone still building OOo with tcsh?

2007-10-08 Thread Volker Quetschke
CC'ing ESC and [EMAIL PROTECTED], please reply to [EMAIL PROTECTED] only.

Hi,

while working on some build feature/improvement for OOo W32 builds
I realized that we have quite a lot of special casing of tcsh vs. bash.

Is that still needed? I would like to remove the support for tcsh
builds if possible. Opinions?

  Volker

-- 
= http://wiki.services.openoffice.org/wiki/Debug_Build_Problems  =
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D



signature.asc
Description: OpenPGP digital signature


Re: [tools-dev] OOo source split

2007-10-08 Thread Jan Holesovsky
Hi Ruediger,

On Monday 08 October 2007 17:36, Rüdiger Timm wrote:

  During the OOoCon, Petr had a presentation about the OOo package
  splitting. The most important part for a (Linux) package maintainer was
  to be able to build parts of OpenOffice.org separately; the thing is that
  with all the localizations, we are unable to get the build times under
  some 7 hours.  But the build could be done nicely in parallel (on the
  level of machines, not processors) if the sources were split correctly,
  with correct rpms and -devel rpms [of course, applies to debs as well
  ;-)].  And of course, the -noarch

 Sorry, I do not understand this. How do you want to build f.e.
 ooo-bootstrap, ooo-libs-core, and ooo-apps-writer in parrallel?
 Bootstrap stuff like dmake or solenv is needed everywhere. Building
 writer needs nearly all lower libraries in place.

Sorry, it seems I should have been more verbose.  As you can see below, I 
don't want these particular build in parallel, their order is fixed:

  ooo-bootstrap
  ooo-libs-3rdparty
  ure
  ooo-libs-guitoolkit
  ooo-libs-core

And from this point:

  [the rest in whatever sequence/in parallel]

It's the ooo-apps-writer, ooo-apps-calc, ... ooo-l10n that could be built in 
parallel and on different machines.

Why don't I want to merge the 'fixed order' ones into one module?  Simply 
'divide et impera' ;-)  They contain stuff that belongs more or less 
logically together.  Eg. I believe we can shrink ooo-libs-core by just making 
some things better, but it's hard to start when one is overwhelmed by the 
amount of modules.

Regards,
Jan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[tools-dev] Re: [council-esc] Is someone still building OOo with tcsh?

2007-10-08 Thread Pavel Janík

Is that still needed? I would like to remove the support for tcsh
builds if possible. Opinions?


FWIW: I have moved to using bash this weekend...
--
Pavel Janík


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]