Thorsten Behrens wrote: > bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote: >> I started a new wikipage here: >> http://wiki.services.openoffice.org/wiki/Build_Environment_Effort/New_Build_System_Requirements >> >> collecting the major requirements for a new build system and what needs >> to be done to implement these requirements with GNU make and CMake >> (those two currently seem to be the only serious contestants). If you >> find additional requirements, feel free to add them to the page. >> > Nice page, thanks Björn! > > Though I think the section about debuggability appears a bit, err, > skewed - I would think none of the contestants are "easily > debuggable" to the common man, when it comes to the internals. ;)
I agree that for the "common man" most non-trival makefiles ar hard to understand, let alone debug. But IMHO it's a fair assumption that understanding/debugging only one file is easier than doing the same for two (the generator and the working file). If a build breaks due to a makefile, you first have to the root cause in the "native" make file, and in case of a CMake/OOo combo it means that for OOo you must be able to do that in two different systems (GNU Make and vcproj). Then you have to find out what caused the problem in the CMake makefile and how to avoid it. That's definitely more work to do than doing the same in a GNU makefile alone. This doesn't rule out CMake as a serious competitor, but it shows that its main benefit (being able to build with VS on Windows) comes at a price. > Having lean dependencies is also nice, but more of a runner-up > criteria for me - it would prolly only make a little dent in the dep > list OOo has anyway... Well, we have to start somewhere, haven't we? Lately I gained some experience with dependencies in OOo and reducing them. IMHO it's easier to understand how the different parts of OOo work together the more the complexity of the dependencies is reduced. This helps new developers to understand. And even the more experienced developers benefit from the better maintainability. So I think that aiming for leaner dependencies (not only) in the long run is a worthwile goal and I wouldn't consider any change in the build system that wouldn't go for it. Whether it's the number one or the number two priority doesn't matter for me: IMHO it's a must have priority. As always, YMMV. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "nospamfor...@gmx.de". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org
