[Cook] Multiple cook files in a project

[Kyle Loveless]

Thanks for the quick reply Peter.

I took a look through the paper and seems to make sense to me. What I would
like to do is not use cook recursively, but just have cookbooks that are
split over different directories(so the zlib library has the zlib related
targets etc..) but would be "binded" together into a single cookbook when
cook is run.

This page: http://evbergen.home.xs4all.nl/nonrecursive-make.html, which you
link to, provides information about implementing a 'modular' Makefile which
appears to solve the issue of make not running in the same directory as the
module.

As a quick hack(without using a stack as that example does, so this
isn't robust) having:
search_list = [dir [pathname [__FILE__]]];
at the top of my cookbook lets me run cook from another directory.

Neither of these, however, solve the issue of variable names colliding (for
either make or cook). What might be ideal is for the individual modules to
list 'exports' of what build rules they wish to publicize and the
importer/including cookbook can import those rules (and perhaps prepend a
unique value to all the rules).

Any more thoughts on how to solve these issues? Perhaps I'm trying to use
cook in an unexpected way.

Thanks,

Kyle

On Thu, Sep 15, 2011 at 1:22 AM, Peter Miller <peter.miller.aus at gmail.com>wrote:

> On Thu, 2011-09-15 at 00:01 -0400, Kyle Loveless wrote:
> > >From what I can tell from the tutorial, it looked like the normal use of
> > cook is to use a single cookbook for the entire project.
>
> This is why...
> http://miller.emu.id.au/pmiller/books/rmch/
>
>
> --
> Peter Miller <peter.miller.aus at gmail.com>
> _______________________________________________
> Cook-users mailing list
> Cook-users at lists.auug.org.au
> http://lists.auug.org.au/listinfo/cook-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.auug.org.au/pipermail/cook-users/attachments/20110916/8c078903/attachment.html>