From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Building dependencies.
Date: Thu, 20 Sep 2001 13:34:14 -0400 [thread overview]
Message-ID: <200109201734.f8KHYJw08873@new-york.lcs.mit.edu> (raw)
> For most Un*x C compilers I used there is -M flag which outputs list of
> sources
> with header dependencies in Makefile format, which later could be
> included
> in Makefile.
We tend to keep things simple, with one header
file for a whole program, or two if we split data
from function declarations. Then we just make
everything depend on the header file (or both headers).
Look at, say, /sys/src/cmd/acme/mkfile.
Russ
next reply other threads:[~2001-09-20 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 17:34 Russ Cox [this message]
2001-09-20 17:44 anothy
2001-09-20 18:28 Alexander Indenbaum
2001-09-21 2:47 ` Boyd Roberts
2001-09-21 8:40 ` Douglas A. Gwyn
2001-09-21 9:14 ` Boyd Roberts
2001-09-21 16:06 ` David Lukes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200109201734.f8KHYJw08873@new-york.lcs.mit.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).