public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: stus@deimus.com.au (Stuart Summerville)
To: help-gcc@gnu.org
Subject: dmake, GNU make, gcc, and auto-dependencies
Date: Mon, 06 Dec 1999 04:43:00 -0000	[thread overview]
Message-ID: <384ba7f4.91964227@vic.nnrp.telstra.net> (raw)

Hi there,

I'm trying to get auto dependencies working amongst gnu make (V3.76 or
so), dmake (4) and gcc (ver?). The gnu make manual (at www.gnu.org)
suggests creating a pattern rule that will create a .d makefile
(containing dependencies for that file) for each source file, & then
"including" that .d file into the main makefile before the source is
built.

Question: How does one stop 'make' from including the .d files if
they're not built yet? For a small 1 file test project (could it be
smaller?), I include the .d file, but its either an old one, or isn't
even built yet.

Another question: The gcc manpage states that the -MD switch will
generate the corresponding .d file, *and* compile the source file. In
doing so, does the contents of the .d file not affect the compilation
of the source file? If not, does that not put the auto-generation of
the dependency rule one step behind in the compilation process? ie.
Shouldn't the generation of the .d file be done in one step, for
subsequent use by make in determining whether to compile the source?

Thanks for any help,

sTu.

WARNING: multiple messages have this Message-ID
From: stus@deimus.com.au (Stuart Summerville)
To: help-gcc@gnu.org
Subject: dmake, GNU make, gcc, and auto-dependencies
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <384ba7f4.91964227@vic.nnrp.telstra.net> (raw)
Message-ID: <19991231222400.gw_8A3sV8fGya3xOp8hx2mwTz1yZaVwN5pIm9gwyqgg@z> (raw)

Hi there,

I'm trying to get auto dependencies working amongst gnu make (V3.76 or
so), dmake (4) and gcc (ver?). The gnu make manual (at www.gnu.org)
suggests creating a pattern rule that will create a .d makefile
(containing dependencies for that file) for each source file, & then
"including" that .d file into the main makefile before the source is
built.

Question: How does one stop 'make' from including the .d files if
they're not built yet? For a small 1 file test project (could it be
smaller?), I include the .d file, but its either an old one, or isn't
even built yet.

Another question: The gcc manpage states that the -MD switch will
generate the corresponding .d file, *and* compile the source file. In
doing so, does the contents of the .d file not affect the compilation
of the source file? If not, does that not put the auto-generation of
the dependency rule one step behind in the compilation process? ie.
Shouldn't the generation of the .d file be done in one step, for
subsequent use by make in determining whether to compile the source?

Thanks for any help,

sTu.

             reply	other threads:[~1999-12-06  4:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-06  4:43 Stuart Summerville [this message]
1999-12-06  7:19 ` Paul D. Smith
1999-12-06 16:28   ` Stuart Summerville
1999-12-06 16:37     ` Stuart Summerville
1999-12-06 20:31       ` Paul D. Smith
1999-12-31 22:24         ` Paul D. Smith
1999-12-31 22:24       ` Stuart Summerville
1999-12-31 22:24     ` Stuart Summerville
1999-12-31 22:24   ` Paul D. Smith
1999-12-31 22:24 ` Stuart Summerville

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=384ba7f4.91964227@vic.nnrp.telstra.net \
    --to=stus@deimus.com.au \
    --cc=help-gcc@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).