Stephan Bergmann schrieb: > Mathias Bauer wrote: >> Rüdiger Timm schrieb: >>> OK. If that's all, 'make it easy to build SDK and URE from scratch >>> independently from OOo', than I am fully with you. It should be possible >>> to check out just a needed subset of modules and build them. Without the >>> need to go through the whole tree just because you need >>> 'instsetoo_native'. But, that's only the first of four paragraphs >>> Stephan wrote concerning 'at build time'. >> >> Yes, I only presented my personal POV. For users and developers of OOo >> there wouldn't be much they could get from separated builds. That's >> clearly something for people that don't want to build OOo. So for me the >> ability to build and work on URE and ODK separately while still keeping >> the OOo build environment would be sufficient. Stephan's mileage may >> vary of course. > > One idea behind the separation of URE and OOo is that you have one URE > installed on your machine and potentially many other applications that > use it (OOo, an ODF toolkit in whatever form, etc.). Sine URE and OOo > are potentially deployed into different locations (e.g., > /opt/openoffice/ure vs. /opt/openoffice2.2), this means that the > OOo-specific code will no longer find the general URE code "right next > to it." And that would also probably have implications on the build > environment, as I detailed in my original post. > > Making URE more easily buildable inside the current OOo build > environment is one possible (first) step. The complete picture would go > further, however, and that is where Rüdiger's concerns would kick in.
Understood, but I think we should start with the first step as it seems to be uncontroversal and it already helps a lot. When we start to implement the complete picture it should be possible to address any concerns that still might exist then. So if people could build the URE and the SDK easily they would be able to use it as we wanted them to use it. Wether we deployed OOo in a way that allowed to share a common URE installation later on shouldn't be important currently, though it surely should be the final goal if we take the idea of the ODF toolkit seriously. I think if Rüdigers' concerns were still valid they would be a clear sign that the separation between the URE and OOo is not really done and that there are still too much dependencies. OTOH if both indeed are separated enough the necessary changes in the build environment shouldn't make problems. Why should anybody have one CWS that contains sources from OOO *and* URE then? Or do I overlook something? Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
