[Cook] Question about Howto.cook ?

[Fredrick Paul Eisele]

You can do what you ask, but you probably shouldn't.
Read...
http://www.pcug.org.au/~millerp/rmch/recu-make-cons-harm.html
...it is by the author of aegis and cook.
It is very good at explaining why separate makefiles is a "bad idea".


That being said, it is probably good to have multiple recipe fragments...
#include "hello/Recipe"
...included from your main cookbook (e.g. Howto.cook Cookbook).
Each fragment controlling the building of a particular subsystem.


Karl.Schmitt at dfs.de wrote:

>
> Dear Folks,
>
> I am evaluating Aegis and Cook for the use
> in our commercial project so far I was successful
> to establish a directory structure and placed
> C++ source files in them. Now I am trying to
> create a Howto.cook file to compile
> and link my C++ sources. Here comes the question
> the Cook tutorial just uses one Howto.cook file
> for the whole project while with 'make' we had
> a 'Makefile' in very subdirectory. In case I only
> want to build the content of a specific sub directory
> what should I do. How does it work? If there is
> no Howto.cook file how does cook know to build
> the content?
>
> Karl
>
>
>
> DFS Deutsche Flugsicherung GmbH
> Unternehmenszentrale
> Am DFS-Campus 10
> D - 63225 Langen
>
> Tel.: +49-(0)6103-707-0
> Internet: http://www.dfs.de