link: "Recursive Make Considered Harmful"

[Simon 'corecode' Schubert]

On Monday, 10. January 2005 22:05, Antonio Vargas wrote:
> I can but wonder if ths simple scheme would work:
>
> 1. We make some way to do #include on a makefile
>
> 2. When we #include a makefile, we alter it's target and dependencies
> so that they get the proper path
>
> 3. At the end of reading the top-tree makefile memory has a master
> makefile and we don't have to change any of the inner ones.

that's what i've been thinking about, too.

> I'm not that big a make hacker, but it can't be that bad internally...
> did I miss something totally obvious???

yes: make is evil code to the max (pun). thankfully max is cleaning up make 
and maybe in the end we can figure out something like this.

cheers
  simon

-- 
/"\
\ /
 \     ASCII Ribbon Campaign
/ \  Against HTML Mail and News
Attachment:
pgp00001.pgp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgp00001.pgp
Type: application/octet-stream
Size: 187 bytes
Desc: "Description: PGP signature"
URL: <http://lists.dragonflybsd.org/pipermail/kernel/attachments/20050110/d4faf11b/attachment-0020.obj>