Date: Tue, 19 Jun 2001 22:26:20 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: Eric Rudd Message-Id: <2561-Tue19Jun2001222620+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9 CC: djgpp AT delorie DOT com In-reply-to: <3B2F9AF2.2F342792@cyberoptics.com> (message from Eric Rudd on Tue, 19 Jun 2001 13:33:22 -0500) Subject: Re: make and autodependency thing References: <3B2ED16B DOT ADE81A9B AT galacticasoftware DOT com> <9gnme8$7mb$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <3B2F9AF2 DOT 2F342792 AT cyberoptics DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Eric Rudd > Newsgroups: comp.os.msdos.djgpp > Date: Tue, 19 Jun 2001 13:33:22 -0500 > > In the Borland make, the .autodepend statement causes the make program to > examine #include statements to figure out dependencies in C programs > automatically, even if there are recursive #includes. It also digs into .LIB > library file headers for information about the dates of library members (as > opposed to the date of the .LIB file itself). GNU Make does the same if you designate targets as being library members. > I found the > .autodepend statement a lot more convenient than using -M during compilation > and having a bunch of extra files to include, and wish GNU make had something > comparable. Such a feature would require Make to understand every programming language where such include directives are available. That's why GNU Make uses GCC to do that: that way, it doesn't need to know anything about the source language.