Xref: utzoo comp.sources.wanted:2837 comp.lang.c:5821
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!hao!oddjob!gargoyle!ihnp4!cuuxb!mmengel
From: mmengel@cuuxb.ATT.COM (Marc W. Mengel)
Newsgroups: comp.sources.wanted,comp.lang.c
Subject: Re: Desperately Seeking Makefile Maker
Message-ID: <1454@cuuxb.ATT.COM>
Date: 23 Dec 87 22:14:34 GMT
References: <1034@cpocd2.UUCP> <538@silver.bacs.indiana.edu> <3133@bunker.UUCP>
Reply-To: mmengel@cuuxb.UUCP (Marc W. Mengel)
Organization: AT&T-DSD, System Engineering for Resellers, Lisle IL
Lines: 22
Keywords: makefile

In article <538@silver.bacs.indiana.edu> creps@silver.UUCP (Steve Creps) writes:
>In article <1034@cpocd2.UUCP> nate@cpocd2.UUCP (Nathan Hess) writes:
>>	Is there a program available that creates makefiles, preferrably
>>	written in C?
>
>You could say something like this:
>fgrep #include *.c *.h | awk -f makefile.awk >makefile

Well, you could do what the maketd utility floating around Purdue
University did, and use the C preprocessor to include all of the
files for you, take the preprocessed output and grab all of the

# 1 "foo.h"
# 1 "/usr/include/bogus.h"

lines out of the file, and use them to generate your dependency lines.
It works quite well. (Maybe someone at Purdue would like to (re?)post
it...
-- 
 Marc Mengel	

 attmail!mmengel
 ...!{moss|lll-crg|mtune|ihnp4}!cuuxb!mmengel