On Sat, Feb 14, 2009 at 5:00 PM, Jussi Pakkanen <[email protected]> wrote: > On Sat, Feb 14, 2009 at 5:21 PM, Christian Lohmaier > <[email protected]> wrote: > >>> I have written a Python script that tries to convert OOo's dmake build >>> system to CMake. >> >> Please start off with your motivation on why you'd want to do that in >> the first place. > > Compared to dmake, CMake has the following advantages for OOo. > > - actively being developed
OOo's dmake is being fixed as well if there are problems, so no real benefit. actively being developed = might break old makefiles from one release to another? No, thanks... > - used widely and thus known by lots of people dmake is very similar to make and that is used and known by even more people, so no real benefit here either. > - native support for all major platforms and IDEs OOo is huge, you will never be able to use an IDE for OOo development (IMHO), so I don't see any benefit here either. > - cross-platform autoconf replacement How is that relevant for OOo? OOo uses configure, environment variables and "static" makefiles. > - straightforward syntax, no shell magicks required (but you can use > them if you want to) Please give an example where "shell magic" is needed and how that same construct would look like in cmake. > [...] > A recurring theme in OOo conference presentations and similar material > seems to be that hacking on OOo is hard for newcomers partly because > it is such a complex beast to build. Making it easier could bring in > more contributors. having different maketool will not help. I see no difference whether the user types "dmake" or "cmake". So how would a different maketool make it easier for newcomers? ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
