[Cook] Large builds

kristof at provost-engineering.be kristof at provost-engineering.be
Mon Jul 2 19:31:17 EST 2007


Hi,

I'm making a prototype for a build system with a few different tools.
The idea it to figure out which tool would be the best choice for us.
The current list includes ClearMake (a make clone included with
ClearCase), GNU Make and Cook.

So far I'm quite impressed with Cook, but I've still got a few
problems/questions.

(1) I'm going to a non-recursive system, so all directories will have a
cook file which includes top.cook (at the top of the file) and
bottom.cook (at the bottom). I'd like to assign the SRC variable from
each of those files to a variable [module_path]_src (e.g.
src/lib_0_src) automatically. I don't want to rely on anything defined
in the directory cookfile. In GNU Make this can be done using the
MAKEFILE_LIST variable, but I can't find anything like it in Cook.

(2) I'd like to rebuild files if the compile statement changes. Does
cook have anything to make this easier than the GNU make approach? (Like
this http://www.cmcrossroads.com/content/view/6528/120/ )

(3) Does anyone have any samples of large build systems I could look at?

(4) I'd like to separate the build configuration (which
features/module/source files to take along) from the build system.
Can you recommend any tools, or can cook
help me out too? As this is an embedded target I'm not interested in
presence of header files, supported features, ... which most
configuration systems seem to be designed for (ie. Autoconf). I'm
thinking of something very much like the Linux kernel configuration
system.


Thanks,
Kristof



More information about the Cook-users mailing list