Makefile analyzer

[Ted Gould]

--=-FL82jiX8hxBUdaayQCPI
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2003-05-13 at 20:44, Alan Dayley wrote:
> I have many (40+) makefiles that build different binaries from the same b=
ase=20
> of 30-ish source files.  I have been charged with documenting exactly whi=
ch=20
> binaries are created from which source files.  Not a dependency tree, jus=
t a=20
> list for each target.  Yep, all the info is in the makefiles but a=20
> non-programmer can't read that.

I don't know of an analyzer, but what I'd probably do to solve the
problem is write a little script that would run in place of gcc in the
make files.  When it gets run it just appends the name of the file it
was supposed to compile into another file.  This way, you'd just run
make to find out what files are used.

		--Ted

--=-FL82jiX8hxBUdaayQCPI
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA+wfUsLE335pRPGp0RAqb0AJ9YTcWnF8D80Vi4HCM50YNdG191VQCgk9UW
yxbSZ8bCUNoZXa69qvk76nY=
=Zy7J
-----END PGP SIGNATURE-----

--=-FL82jiX8hxBUdaayQCPI--