On Mon, Feb 1, 2010 at 3:09 PM, bjoern michaelsen - Sun Microsystems - Hamburg Germany <[email protected]> wrote:
> 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. There are some inconsistencies with the page. I'll post them here rather than directly to the page to prevent an editing war. Firstly under dependencies it says "[CMake] is not usually available on the default install of many platforms." and then a bit further down "One might consider using Python as a tool for _all_ non-standard build tasks. Python is easy to distribute and install on all platforms." This is somewhat conflicting: CMake is just as available and easy to install as Python on every (meaningful) platform. Another point is "However, there are many cases where the current build process depends on a large set of external tools like bash, awk, findutils, coreutils." Does the actual building require these or is it more of a case of "need these, because dmake/build.pl needs these"? In my OOo CMake experiment I built idlc, generated urd, Java etc all without needing the tools listed. Perhaps someone could post an example from current build where these are used. If one is going to go the CMake route, the long term smart thing to do is probably to convert these existing things into CMake's internal syntax. It has quite a rich library of stuff. Yes, this is more work but the good news is that you don't have to do it at once. First you can replicate the old build system by calling the awk scripts and what have you and then replace them one by one. With CMake macros and some discipline this is straightforward. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
