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 helper" to select the parts you want to develop on, > only things dependent on these may need to be build, everything else > may be pre-build / abandoned. 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 understandable requirement for a build-helper at that stage (assuming we're talking about per module of per module-bundle pre-build/solvers) If you're thinking about build-helpers, then e.g. jhbuild route might be worth a look http://library.gnome.org/devel/jhbuild/unstable/introduction.html.en and follow an alternative route where each project/module group is a toplevel project with a little configure.in for "find the compiler"/"tell me where the sdk is"/"where should I make install to". Conceptually each *always* uses the headers of, and links against the libraries of prebuilt dependencies, and if there's a need for a build-helper then its a separate toplevel tool which takes care of the case of someone wanting to build the entirety from scratch. C. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
