From: "Richard L.F. van Paasen" <R DOT L DOT F DOT v DOT Paasen AT stud DOT tue DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: Make files
Date: Sun, 22 Sep 1996 21:26:40 -0700
Organization: University of Technology Eindhoven
Lines: 28
Message-ID: <32461180.29C6@stud.tue.nl>
Reply-To: R DOT L DOT F DOT v DOT Paasen AT stud DOT tue DOT nl
NNTP-Posting-Host: annex1s56.urc.tue.nl
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Hi, (subject: write a generic makefile)

I've downloaded the DJGPP software recently. I am a former Borland C++
user, who's used to projects instead of makefiles. The beauty of 
Borlands project files is that the only thing you have to tell
the compiler is the sources and external objs and libs you're using.
It figures out all depedencies (rules etc.) by itself, even from nested 
header files. (of course it has drawbacks too).

I've tried to write a makefile that does the following:

- take all *.cpp and *.c and *.asm files in a given directory (yes,
all!)
- take some named .cpp .c and .asm files
- compile them, when they need to be compiled (ie. when header files and
the
  source itself are changed)
- compile the whole thing into an archive (or executable), add some libs
  and objs to it (ehh, I mean .a and .o files)

But man, this seems not straightforward for a non-unix programmer. Is
here
someone who has written such a (generic) makefile, and who wants to
share it
with me (and all newbies that read this newsgroup) ? I'd be glad to
hear.

Richard van Paasen.