Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Mar 2005 04:08:16 +0000
From:      Jonathon McKitrick <jcm@FreeBSD-uk.eu.org>
To:        Chuck Robey <chuckr@chuckr.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: How to include header files in makefiles
Message-ID:  <20050319040816.GA58002@dogma.freebsd-uk.eu.org>
In-Reply-To: <423B03F7.70405@chuckr.org>
References:  <20050318031137.GA99419@dogma.freebsd-uk.eu.org> <423B03F7.70405@chuckr.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 18, 2005 at 04:38:15PM +0000, Chuck Robey wrote:
: 1) relative addressing means you have to be forever translating paths in 
: listings, and very often the number of include paths gets to be rather long.

Okay, I can fix that easily.

: The Make(1) man page doesn't show "include", the advertised command is 
: ".include".  If you use .include, then you can modify your make, if you 

Also fixable.

: >How can I include the .h files so the .c files are recompiled when the
: >header files they require are changed?  GNU make has 'make depend' but I'd
: >like a better, BSDmake-centric way, if possible.
: 
: Well, did you look at the files in /usr/share/mk, and specifically 
: bsd.dep.mk?  You can even use the FreeBSD sources to figure out (to use 
: as examples) how things should work.

This is the key I want to get working.  I'll take a look at those files, but
they are pretty deep.

: I honestly keep on switching back and forth, between thinking that the 
: best make is bmake, or gmake.  They both have key items that make them 
: uniquely better.

I haven't decided yet.  Most BSD people are (predictably) anti-gmake.  I
have to use gmake for a Linux project I'm on.

Jonathon McKitrick
--
My other computer is your Windows box.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050319040816.GA58002>