<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>RE: [Cook] Large builds</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>
<P><FONT SIZE=2>> -----Original Message-----<BR>
> From: cook-users-bounces+jpendergraft=sjm.com@auug.org.au on behalf of kristof@provost-engineering.be<BR>
> Sent: Mon 02-Jul-07 04:31<BR>
> To: cook-users@auug.org.au<BR>
> Subject: [Cook] Large builds<BR>
<BR>
> Hi,<BR>
<BR>
> (1) I'm going to a non-recursive system, so all directories will have a<BR>
> cook file which includes top.cook (at the top of the file) and<BR>
> bottom.cook (at the bottom). I'd like to assign the SRC variable from<BR>
> each of those files to a variable [module_path]_src (e.g.<BR>
> src/lib_0_src) automatically. I don't want to rely on anything defined<BR>
> in the directory cookfile. In GNU Make this can be done using the<BR>
> MAKEFILE_LIST variable, but I can't find anything like it in Cook.<BR>
Normally it is done the other way round, that is the top level cook file includes all the others. There are ways to organize such that you probably won't need such a variable but it can be done quite easily.<BR>
<BR>
> (2) I'd like to rebuild files if the compile statement changes. Does<BR>
> cook have anything to make this easier than the GNU make approach? (Like<BR>
> this <A HREF="http://www.cmcrossroads.com/content/view/6528/120/">http://www.cmcrossroads.com/content/view/6528/120/</A> )<BR>
That would be form of what cook calls a "manifest" dependency. Most commonly used for source lists, but can be used for anything.<BR>
<BR>
> (3) Does anyone have any samples of large build systems I could look at?<BR>
Does a system that manages 2000 source (c++) files in 22 sub-systems and builds around 200 binaries both optimized and non-optimized across multiple architectures all in parallel count?<BR>
<BR>
> (4) I'd like to separate the build configuration (which<BR>
> features/module/source files to take along) from the build system.<BR>
> Can you recommend any tools, or can cook<BR>
> help me out too? As this is an embedded target I'm not interested in<BR>
Cook can help out here because you can easily reference architecture specific files if need be for your build - yet another organizational thing.<BR>
<BR>
> Thanks,<BR>
> Kristof<BR>
<BR>
Jerry Pendergraft voice:651-523-6935<BR>
St.Jude Medical mobil:651-491-0163<BR>
Atrial Fibrillation Division email:jpendergraft@sjm.com<BR>
1350 Energy Lane<BR>
St.Paul, MN 55108<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>