--nextPart3203370.IIAGRH1DXW
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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=
=20
and maybe in the end we can figure out something like this.
cheers
simon
=2D-=20
/"\
\ /
\ ASCII Ribbon Campaign
/ \ Against HTML Mail and News
--nextPart3203370.IIAGRH1DXW
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQBB4vTWr5S+dk6z85oRAlYVAKC2SNGa3Qlrq8GRcNaUGRn68cHfvwCaAhMJ
/KCv2pp3KJJXTgGqmDmYXn8=
=zk0U
-----END PGP SIGNATURE-----
--nextPart3203370.IIAGRH1DXW--