Caolán McNamara wrote:
On Thu, 2009-04-30 at 16:34 +0200, Kay Ramme - Sun Germany - Hamburg
wrote:
The above sounds a little like the current single hierarchical build
tree with a single toplevel configure script but with a bunch of
--enable-prebuild-vcl --enable-prebuild-i18npool etc
options
OOo Folks,
by now OOo has been regarded as the only real alternative office suite,
sometimes hard to build, often admired for its feature completeness,
somewhat beaten because of the memory footprint, understood to have one
of the most classical graphical user interfaces ever, loved to recover
Hi Kay, Xiuzhi, all,
Kay Ramme wrote:
OOo Folks,
[...]
Many words may be used for OOo, though small is not with them :-)
OOo is a huge project, with lots of code and a more or less monolithic
architecture. (Even :-) the ESC understands that size does not only has
advantages (though it
Caolan,
Caolán McNamara wrote:
On Thu, 2009-04-30 at 10:29 +0200, Kay Ramme wrote:
- Add missing/useful configuration switches (e.g. for headless support).
FWIW vcl headless support is always just built at the moment, so not
sure of its role an example of a missing/useful configuration
Caolán McNamara wrote:
On Thu, 2009-04-30 at 14:07 +0200, Kay Ramme - Sun Germany - Hamburg
wrote:
I should have been more precise - what I mean is not only to add more
enable/disable switches, but to add/change switches to support something
as build/pre-build/disabled.
utilize the build
On Thu, 2009-04-30 at 16:34 +0200, Kay Ramme - Sun Germany - Hamburg
wrote:
The above sounds a little like the current single hierarchical build
tree with a single toplevel configure script but with a bunch of
--enable-prebuild-vcl --enable-prebuild-i18npool etc
options and an