[9fans] Building dependencies.

[9fans] Building dependencies.

[Alexander Indenbaum]

[-- Attachment #1: Type: text/plain, Size: 285 bytes --]

Hello!

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.

How do I do something similar on Plan9?

Thanks in advance for your help,
        Alexander



[-- Attachment #2: Type: text/html, Size: 582 bytes --]

Re: [9fans] Building dependencies.

[Boyd Roberts]

Building dependencies.> For most Un*x C compilers I used there is -M flag which outputs list of
> sources with header dependencies in Makefile format ...

yeah i remember that.  came out of 6th Ed, right?

Re: [9fans] Building dependencies.

[Douglas A. Gwyn]

Boyd Roberts wrote:
> yeah i remember that.  came out of 6th Ed, right?

Not likely; 6th Edition UNIX didn't have "make".

Actually I never heard of the cc -M flag and am surprised
to hear that "most" UNIX C compilers supported it.  It's
not documented in the manuals for 6th, 7th, 8th, 9th, or
10th Edition UNIX, nor for any release of UNIX System V
for which I have documentation, nor in SVID Issue 3.

Re: [9fans] Building dependencies.

[Boyd Roberts]

From: "Douglas A. Gwyn" <DAGwyn@null.net>
> Boyd Roberts wrote:
> > yeah i remember that.  came out of 6th Ed, right?
>
> Not likely; 6th Edition UNIX didn't have "make".

i know.  i was being sarcastic.

Re: [9fans] Building dependencies.

[David Lukes]

> Actually I never heard of the cc -M flag and am surprised
> to hear that "most" UNIX C compilers supported it.

Well, IIRC, it's another Berkeleyism that has
(like everything else) been carried across into the Gnuniverse.

The reason you need it is because of #ifdef ... #include
type madnesses, otherwise sed did a fine job.

Cheers,
	Dave.

Re: [9fans] Building dependencies.

[anothy]

// 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).

while i agree this is the best approach to building
systems in most cases, i ocasionally have to deal with
alien code. much, much code i've run accross isn't
built with anything approaching simplicity in mind,
nor do the makefiles tend to be readable, useful, or
workable under APE. i'd love to be able to generate the
list of dependancies and roll my own ma?ke?file.
-α.

Re: [9fans] Building dependencies.

[Russ Cox]

> 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