Kay, Christian,
Le Thu, 30 Apr 2009 11:43:02 +0200, Kay Ramme <[email protected]> a écrit : > > Hi Charles, > > Charles-H. Schulz wrote: > > > > I have read the wiki pages, and while I'm all for this kind of > > vision, I am not sure if I understood this correctly: > > modularization for you seems to essentially takes place at the > > building level, and not so much an application level. This would > > mean, for instance, that we could have several "sub-versions of > > OOo", but this would be different from having an office suite with > > "modular" applications (with less common dependencies, etc.). Am I > > getting this right or am I making things too complex? > You get it right, though you are missing the pre-build thing ... > > First goal is to ease building OOo and variants in a static way, by > developing a "build helper" and by extending/adapting the configure > script as well as the code. > > If you have taking a look at what "configure" currently offers wrt > Mozilla, you see that you actually can re-use pre-build binaries. To > improve and simplify the overall build experience, we would like to > generalize this approach to other parts of OOo as well. Some obvious > candidates for this are the build-system and Uno, as developers > typically don't change them so much, thus having them pre-build would > reduce build times etc. > > To make things simple, we just would like to achieve the above in a > static way, e.g. during "configure". If it proves viable, we > certainly would like to convert this approach to be more dynamic, > e.g. offering the different pre-build modules as extensions (or > similar) ... > > Let's just start with something simple, things tend to become complex > over time anyway :-) They do indeed. I just wanted to clarify where this initiative was going and you have my support. Best, Charles. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
